Skip to content

fix(ci): serialize local tests — 4Gi dind runner OOMs under parallel browser suites#229

Closed
Jesssullivan wants to merge 1 commit into
mainfrom
fix/gates-serialize-local-tests
Closed

fix(ci): serialize local tests — 4Gi dind runner OOMs under parallel browser suites#229
Jesssullivan wants to merge 1 commit into
mainfrom
fix/gates-serialize-local-tests

Conversation

@Jesssullivan

Copy link
Copy Markdown
Owner

Post-#227, the gates lane executes the browser test suites locally. The jesssullivan-blog-dind runner container is limited to 4Gi memory; parallel local tests (vitest + puppeteer chromium + node suites concurrently, then playwright) intermittently OOM the pod → silent runner death after ~15m (job fails with zero failed steps). Observed on every run of the 4-PR stampede AND a solo rerun; #227's own green run fit by luck.

test:ci-cached --local_test_jobs=1 caps peak memory at one browser at a time. Executor-backed lanes are unaffected (local_test_jobs governs local actions only).

Durable follow-up (operator/GF-side): raise the runner-set memory limit for jesssullivan-blog-dind in the GF overlay (currently limits.memory=4Gi) — tracked in the wave report, TIN-2677 family.

@Jesssullivan

Jesssullivan commented Jul 14, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #228. The unique test:ci-cached --local_test_jobs=1 safeguard from this PR was folded into #228 at signed commit a58489c, together with regression coverage. #228 retains the already-proven Tectonic warmup, bounded local build parallelism, and shared-cache contract, so we have one canonical CI-hardening lane instead of two overlapping branches.

@Jesssullivan

Copy link
Copy Markdown
Owner Author

Closing as superseded by #228; no unique change was discarded.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant