3 Commits

Include renames

Author	SHA1	Message	Date
Vito Sansevero	f707a1abe5	test(browser): keep the reset scratch database in /dev/shm when there is one (#384) ... Throttled runs still waited on the runner's disk while creating and rewriting the scratch database, whose pages were under writeback.	2026-10-27 07:14:49 -07:00
Vito Sansevero	c160b186d7	fix(test): recheck the live data version under the publish's write lock (#384) ... A writer whose transaction was open while the seed ran committed before BEGIN IMMEDIATE returned and its rows were overwritten. The publish now rechecks data_version under the lock, and restores foreign_keys and detaches the scratch database on every error path.	2026-10-27 07:06:33 -07:00
Vito Sansevero	116a66f755	test(browser): seed resets on a scratch copy and publish them in one commit (#384) ... The concept and plain resets made hundreds of committed transactions on the live database; on a slow CI disk they queued behind WAL checkpoint syncs and took 30+ s. Each reset now copies the live database into a scratch database (backup API, no syncs), runs the unchanged seeder against it through an API proxy, and replaces the rows of the tables the seed changed in one live transaction. A commit by another live connection meanwhile fails the reset. tests/browser/reset_equivalence.py proves every reset kind leaves the same rows, files and response as the old path (PM_TEST_SEED_ON_LIVE=1).	2026-10-27 07:02:50 -07:00