From 96966709692407bd487709b4914b744ab1e235b1 Mon Sep 17 00:00:00 2001 From: Jake Bromberg Date: Tue, 19 May 2026 11:55:44 -0700 Subject: [PATCH] Drop bail from integration-test jest config MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit bail: 1 masked the BS#955 cascade pattern — when G4's process-wide TokenBucket drained, the suite reported only the first failing spec (metadata-lml.spec.js) and exited, hiding that subsequent integration specs were also queueing on the same exhausted bucket. With the limiter env vars now correct in both CI surfaces (workflow + compose, BS#957), the suite is stable enough that the diagnostic value of full failure visibility outweighs the CI-minute savings from short-circuiting on first failure. CLAUDE.md doc line updated to match. --- CLAUDE.md | 2 +- jest.config.json | 1 - 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index f348e3cf..384ef1f5 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -217,7 +217,7 @@ npm run test:integration - Location: `tests/integration/**/*.spec.js` - Setup: `tests/setup/integration.setup.js` with `tests/setup/globalSetup.js` - Tests run sequentially (`--runInBand`) because they share show state, DJ sessions, and flowsheet entries -- 30-second timeout per test, bail on first failure +- 30-second timeout per test - Generates HTML report at `tests/report/report.html` ### CI mock diff --git a/jest.config.json b/jest.config.json index e3bb2da0..8458c8e1 100644 --- a/jest.config.json +++ b/jest.config.json @@ -18,7 +18,6 @@ ], "maxWorkers": "50%", "testTimeout": 30000, - "bail": 1, "forceExit": true, "verbose": true }