CI Issue
The Coverage Suite workflow (.github/workflows/coverage-hourly.yml) has now failed twice on main within 15 hours, with different shards failing each time. This is impacting coverage-ratchet gating.
Evidence
- Run 29675971035 @ 2026-07-19T06:09Z — shard 11
##[warning]Shard 11 exited with code 1 (possible OOM); failing test: src/components/namespaces/__tests__/NamespaceAccessPanel.test.tsx > NamespaceAccessPanel refetches access entries after namespace changes
- Run 29703839550 @ 2026-07-19T21:09Z — shards 3, 6, AND 11 failed simultaneously,
merge-coverage job also failed. Different shards failing on the same commit suggests OOM/resource contention rather than a single flaky test.
- Prior main-branch failures on 2026-07-17 (5×) and 2026-07-18 (1×). Baseline is not clean.
Recommendation
- Bump runner size or Node
--max-old-space-size for the shard test jobs (leading candidate given the "possible OOM" warning).
- Alternatively, reduce parallelism per shard (
--pool=forks --poolOptions.forks.maxForks=…).
- If a specific test is legitimately racy (NamespaceAccessPanel refetch), stabilize via
vi.useFakeTimers() + explicit await waitFor(...) boundaries.
Related tracking: bead e3f6c8d4-194 (ci-maintainer).
Filed by ci-maintainer agent (ACMM L6 — full mode)
CI Issue
The
Coverage Suiteworkflow (.github/workflows/coverage-hourly.yml) has now failed twice onmainwithin 15 hours, with different shards failing each time. This is impacting coverage-ratchet gating.Evidence
##[warning]Shard 11 exited with code 1 (possible OOM); failing test:src/components/namespaces/__tests__/NamespaceAccessPanel.test.tsx > NamespaceAccessPanel refetches access entries after namespace changesmerge-coveragejob also failed. Different shards failing on the same commit suggests OOM/resource contention rather than a single flaky test.Recommendation
--max-old-space-sizefor the shard test jobs (leading candidate given the "possible OOM" warning).--pool=forks --poolOptions.forks.maxForks=…).vi.useFakeTimers()+ explicitawait waitFor(...)boundaries.Related tracking: bead
e3f6c8d4-194(ci-maintainer).Filed by ci-maintainer agent (ACMM L6 — full mode)