Repository navigation
[Bug]: ocx-launcher-runtime "missing bundle reaches validated PATH Bun" times out at 5 s under host load #7578
Description
Client or integration
Other
Area
Installation or packaging
Summary
tests/cli/ocx-launcher-runtime.test.ts › Node launcher PATH fallback activation › missing bundle reaches validated PATH Bun times out at the default 5000 ms when the host is busy, so bun run test:changed / bun run test reports it red. Run alone on the same tree it passes (77 pass / 0 fail, about 10.6 s for the file). The case spawns real Node and Bun processes, and that cost scales with host load, so a 5 s per-test budget is not reliable on a shared machine. I expected the case to either finish well inside its budget or have a budget that matches the subprocess work it does. I did not raise any timeout locally.
Reproduction
- On macOS with Node available, check out
131eae33b0(PR feat(jev): opt-in session pin keeps a JEV combo session on its decided target #7567's merge head; the launcher code comes from fix(codex): bind CLI update plans to installation content and pre-dotenv transport #7546 ondev). - While another full suite is running on the same machine (here another worktree's
bun scripts/test.tswith--parallel=4, load average about 6–9), runbun run test:changedwith Bun 1.4.3 as the runner. - The case fails with
^ this test timed out after 5000ms.(5121 ms). bun test tests/cli/ocx-launcher-runtime.test.tson the same tree passes.
Version
Commit 131eae33b0e8c4f5506592e8b51bc92c2defb15b (test runner Bun 1.4.3)
Operating system
macOS 27.0 (Apple silicon)
Provider and model
Not provider-specific.
Logs or error output
(fail) Node launcher PATH fallback activation > missing bundle reaches validated PATH Bun [5121.18ms]
^ this test timed out after 5000ms.
42446 pass / 110 skip / 2 fail — Ran 42558 tests across 1953 files. [402.92s]
Screenshots and supporting files
No response
Redacted configuration
No response
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
Activity
Ingwannu commentedon Oct 23, 2026
Tracking the existing focused fix in #7598, which explicitly references #7578. I checked the patch's approach: cold process startup moves to bounded fixture setup, while the measured product deadline and failure semantics remain unchanged. The certificate-runner seam also has a deterministic deadline-error control; a partial
not-trustedstdout after a killed child must still yieldunknown.This is not yet an integration/release claim, and a warm fixture alone would not prove real cold-start service behavior. Current-head hosted CI/native evidence and unchanged negative controls remain required. Keeping this issue open until the corresponding fix is integrated and its scope is verified; no timeout enlargement or live trust-store mutation was performed here.
test: keep cold first-exec and PowerShell start out of two timed cases (
lidge-jun commentedon Oct 24, 2026
Fixed on dev by #7598 (bd5c2ea): the PATH-fallback cases share one Bun copy warmed in a budgeted beforeAll, so the cold first-exec scan of a fresh binary is no longer inside the timed case. Please reopen if it recurs.