Jacob MacDonald

cc @Markzipan @nshahan

[Here is an example run](https://github.com/dart-lang/build/actions/runs/2658903064), same exact tests and version solve, one passes on 2.18.0-238.0.dev and the other fails on 2.18.0-250.0.dev (you can expand the setup dart step on each...

Not sure how this is related, but another anecdote is that the tests which are opted out of null safety consistently fail, while the opted in tests only fail flakily.

There are no compile time errors, I tried running several times locally but I will try also throttling the network to see if that helps repro the issue. Update: throttling...

> Is there a way I can debug the test running in chrome locally? Two ways, from the `_test_null_safety` directory in the build repo: 1) `dart run build_runner serve test`...

I am not aware of any way to run with a custom SDK on github actions... we can only download the sdks available on google cloud storage.

Trying that here https://github.com/dart-lang/build/pull/3331

Me and Nick spent some more time today looking into this but have hit a dead end. We were able to get some more information though: - The first failing...

Fwiw I have narrowed this down to the commit with this sha 624dd76b6f3af2ea84a0e5acfc5ec02f14b3f666. A custom sdk built from the tag for 2.18.0-246.0.dev passes, and cherry picking in that sha it...

Fwiw I did add some extra logging in a branch of package:test I was using to debug this issue, but it didn't output anything helpful.