Keep CI's /tmp in memory so no test waits on the runner's disk (#299) #300
Loading…
Reference in a new issue
No description provided.
Delete branch "claude/ci-flake-299"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For braid#299. The issue stays open until five CI runs in a row pass, including a push that overlaps a deploy.
What was slow
Small tests that create or close a SQLite file in their own body. Both sync the file to disk, and on a busy runner one sync took a second or more:
test_a_reconnect_backfill_adds_nothing_the_stream_already_delivered, 1.6 s. In run 249 two workers hit it at the same moment.test_migrating_twice_changes_nothing, 1.0 s.Neither test has a wait of its own: locally the reconnect test's whole body takes about 6 ms.
Change
/tmp, where pytest'stmp_pathand the browser tests' servers keep their files, is now a 1 GB tmpfs, where a sync costs nothing. The backend tests write about 30 MB there. A first step fails the job if/tmpis not a tmpfs, so a runner that dropped the option is caught at once.storefixture, as every other store test does. The fixture moves fromtests/store/test_store.pytotests/conftest.py. On its own this only moved the failure to another test (run 252), so the tmpfs is the fix.Checked
./tools/test.shpasses locally in 16 s.🤖 Generated with Claude Code
Build the reconnect backfill test's store in a fixture (#299)to Keep CI's /tmp in memory so no test waits on the runner's disk (#299)