"migrate: after > mirror: …" in test/migrate-after.test.ts went red on pulls #4426, #4445, #4443, #4446 and #4348 — pulls that never touched its code. It depends on wall-clock time or ordering on a loaded check machine.
Done:
[ ] the three mirror cases (no write at migration then one push after a landing; work branches never go to the source; a source that moved is not overwritten) wait for the push they assert, not a 90 s poll loop
[ ] it waits on the event it means (a settled promise, a row, a ref), never a fixed sleep or a raw deadline; any time budget goes through the load-proof helper from #4431
[ ] bun test test/migrate-after.test.ts passes 20 times in a row under scripts/flake-hunt.ts (or with 8 copies running at once), and the pull says how it was run
"migrate: after > mirror: …" in test/migrate-after.test.ts went red on pulls #4426, #4445, #4443, #4446 and #4348 — pulls that never touched its code. It depends on wall-clock time or ordering on a loaded check machine.
Done:
bun test test/migrate-after.test.tspasses 20 times in a row underscripts/flake-hunt.ts(or with 8 copies running at once), and the pull says how it was run