Abort updates immediately when we abort a build due to --stop-on-failure
Otherwise we get screenfuls of output on large builds that look like this (scrolling after the "Stopping here" message):
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
No source update, but the build directory doesn't exist
This is due to the update thread continuing to move forward. This might already be fixed in the make_it_mojo
branch but until that's ready to take over this is just confusing.