wheel-sqlite: BUG-022 regression test, docker-free - #16
Open
Morgandri1 wants to merge 1 commit into
Open
Conversation
|
Deployment failed for project wheel with the following error: Learn More: https://vercel.com/morgandri1s-projects?upgradeToPro=build-rate-limit |
Morgandri1
force-pushed
the
sdk/shm-blocked-regression-test
branch
from
September 6, 2026 17:36
0c5ea13 to
5cf99a2
Compare
PM approved landing this: additive to QA's docker-based ENG-starts- without-shm gate (qa/integration/test_engine_shm.py), not a duplicate -- same failure mode, different technique, no docker required. QA's own comment says the directory-at-the-shm-path fixture "verified to reproduce the production symptom exactly," and that fixture is a filesystem fact, not a container one, so it reproduces here too. Seeds a database already in WAL (the shape that actually crash-looped production -- journal_mode persists in the header, so every boot rediscovers it), blocks the -shm path with a directory, then asserts open_configured(path, false) -- the engine's own mode -- both returns Ok AND accepts a real write, with the pre-existing row intact. Mutation- checked: reverting mode_holds to a bare read-back (dropping the `BEGIN IMMEDIATE; COMMIT` proof) reproduces the exact symptom -- settles back on "wal", the mode that just failed. Does not close qa/BUGS.md #22 -- that stays QA's call once they confirm 1163cc9 live against a fresh image (PM is asking them directly).
Morgandri1
force-pushed
the
sdk/shm-blocked-regression-test
branch
from
September 7, 2026 00:25
5cf99a2 to
9706f2e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PM approved (per handoff/status): a docker-free unit test proving
open_configuredrecovers on a volume that cannot host a-shmfile — additive to QA's docker-basedENG-starts-without-shmgate (qa/integration/test_engine_shm.py), not a duplicate. Same failure mode QA's fixture reproduces (a directory sitting where sqlite wants-shm), different technique, no docker needed, runs in milliseconds under plaincargo test.Seeds a database already in WAL (the shape that crash-looped production —
journal_modepersists in the file header), blocks the-shmpath with a directory, then assertsopen_configured(path, false)(the engine's own mode, never exclusive) both returnsOkand accepts a real write, with the pre-existing row intact.Mutation-checked: reverting
mode_holdsto a bare read-back (dropping theBEGIN IMMEDIATE; COMMITwrite-proof) reproduces the exact symptom — the test fails, settling back on"wal", the mode that just failed.Does not close
qa/BUGS.md#22 — that's QA's call to make once they confirm1163cc9live against a fresh image (PM is messaging them directly per their own status update).Test plan
cargo test -p wheel-sqlite— 13 passedcargo clippy -p wheel-sqlite --all-targets -- -D warnings— cleancargo fmt -p wheel-sqlite -- --check— cleancargo build --workspace— clean