Repository navigation
qCRM: demo.test.ts flakes in CI (snapshot never built; warmDemo's error is swallowed) #4122
Description
Seen on PR #4114 (Swift-only change), run https://github.com/QuinnsCode/RustyBuns/actions/runs/42595087695/job/129085786601:
the demo opens on the shared snapshot, keeps a visitor's edit, and writes only what they touched failed at apps/qcrm/test/demo.test.ts:27: expect(DEMO.objects.size).toBe(1) got 0 right after await hourly(app.env), in 6.83ms. The same file passes alone on Bob (bun run builder run apps/qcrm bun test test/demo.test.ts, 2 pass).
hourly in apps/qcrm/src/demo.ts calls warmDemo(env).catch(() => {}), so whatever failed in the full suite is hidden. #4103 (merged 2026-11-09) touched hourly (runScheduled); it may be the trigger, or it may be state shared with another test file. First step: surface the warmDemo error in the test, then find what the full run shares.
Activity
QuinnsCode commentedon Nov 9, 2026
The rerun failed the same way (job 129092752511), so in CI it fails every time, with the same bun 1.4.3 Bob uses. Bob passed the same tree running only test/demo.test.ts, while CI runs the whole qCRM suite. So it is probably state shared between qCRM test files (a module-level cache or gate, or a DEMO key another file already wrote), not timing. It blocks every PR that runs all apps (anything touching packages/), e.g. #4114.
qCRM demo snapshot: cache it per bucket, not once per module (Closes #…
qCRM demo snapshot: cache it per bucket, not once per module (Closes #…