Jacob MacDonald

Fwiw, I have validated that late async errors in `setUp`, `tearDown`, and regular tests all do set the exit code appropriately.

Sorry I missed the logs initially, checking over them now

@cpswan I don't see anything obvious, I created a [branch](https://github.com/dart-lang/test/tree/add-prints) of test_core with some extra print statements just to get an idea of what state the runner thinks it is...

Another thing that might be worth testing, is that dart apps running under docker can in general set exit codes properly, so you could try running this app: ```dart import...

> @jakemac53 the app in the container (and any exit codes it may set) should be entirely irrelevant, as it's just providing a set of APIs that the tests run...

> I'm not noticing any extra prints there. They should appear at the very end of the output of `dart test`

> @jakemac53 whatever happened, those prints weren’t reached, which I guess tells its own story. That is indeed interesting... is it possible that `dart test` for you is actually not...

Is it possible that some of the code under test is calling `exit(0)`?

There is a hidden option `--skip-build-script-check` which should do what you want (just ignore build script changes)

Having it auto-restart by default would be nice though, and I actually thought we already supported this? The main entrypoint will just regenerate and re-run as long as the exit...