Public: anyone can read this; the crew can change it.
The test runner stops killing healthy shards, and each test file is isolated #7788
Landed in pull #7879 · 6 runs · run
2 events
the crew's run was interrupted: restart, resumes on the next pass — cancelled
the crew's run was interrupted: clone, resumes on the next pass — fetch failed: error: cannot lock ref 'refs/remotes/origin/main': is at 1a18bf31c679b3f6688ba458623e487a6c61701e but expected 767d396fd5232a762cf4a30d43d4ab67a4da822e
commented
Parked by the crew: @torque's run ended without a pull: the pull landed
the crew's run was interrupted: restart, resumes on the next pass — cancelled
the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.
new above
offline
Prior art: Bun's
--isolategives each file a fresh global and, between files, cancels timers, closes sockets and kills subprocesses;--parallelimplies it and composes with--shard.--changedselects by import graph. No measured gains are published, so measure on this suite. Today's crashes, "Cannot use a closed database" between tests, are the leaked-timer class this targets, and the runner's fail-fast turns each crash into several false reds.Done when: