id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
22698	runserver does not exit when checks fail	Ben Davis	nobody	Normally I'd think if process of any kind has fatal errors, it should exit with a non-zero status code. If checks result in messages `>= ERROR`, runserver will just hang there until you press Ctrl+C. This is due to the fact that checks are performed in `inner_run()` as opposed to `outer_run()`. Is there a reason why it's done this way, or is this a legitimate bug?	Bug	closed	Uncategorized	dev	Normal	worksforme			Unreviewed	0	0	0	0	0	0