Dart CLI tests that spawn other Dart VMs inherit the debug settings from the test runner

In order to run Dart CLI tests we use the VM and set these env vars:

envOverrides = {
	DART_VM_OPTIONS: "--enable-vm-service=0 --pause_isolates_on_start=true",
};

However since these are env variables, if our tests spawn other Dart/Flutter/Pub processes, they will inherit them:

✓ FlutterTesterDevice can hot reload
Running "flutter packages get" in test_appmVCWmw...
Observatory listening on http://127.0.0.1:54689/

Not only does this make the tests not work, it's difficult to track down if you're not exposing stdout of all of the spawned processes.

There might not be a fix for this:

Run pub using snapshot/VM for pause-on-start that doesn't cascade

Navigation Menu