Repository navigation
[Bug]: resolveCodexRuntime test depends on the host's installed Codex #7403
Description
Client or integration
Other
Area
CLI
Summary
tests/codex-integration/codex-runtime.test.ts › resolveCodexRuntime › treats missing persisted and resolved versions as the same selection fails on clean origin/dev on a developer machine that has Codex installed. It expects "fallback" and receives "installed", so the test reads host state instead of an isolated fixture.
Reproduction
- On a machine with Codex CLI installed, check out clean
dev(dbb908f). bun test --isolate tests/codex-integration/codex-runtime.test.ts- One failure, the same on dev and on feature branches.
Version
dev dbb908f
Operating system
macOS 27 (darwin 27.0.0, arm64)
Provider and model
No response
Logs or error output
error: expect(received).toBe(expected)
Expected: "fallback"
Received: "installed"
(fail) resolveCodexRuntime > treats missing persisted and resolved versions as the same selection
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
github-actions commentedon Oct 19, 2026
Automated translation bookkeeping — detected language: English.
Ingwannu commentedon Oct 20, 2026
Checked against trusted dev
12025981e5a304cdb6b1b54f525ba8554f623977. The assertion concerns resolver source, so the fixture must control every installed/PATH/persisted-runtime candidate, not only clear the persisted version. Please make this case use the existing resolver injection/fixture seams with a bounded fake executable and an isolated candidate search, and retain a separate installed-source control. A machine without Codex passing is insufficient evidence that the test is hermetic. I have not run the host's installed Codex or changed runtime selection.lidge-jun commentedon Oct 23, 2026
Same failure seen again on 2026-10-23 while validating #7567, with an isolated
HOME/OPENCODEX_HOMEand Bun 1.4.3 on macOS 27.0: expected"fallback", received"installed". It also fails on the untouched base9164950d92, so it is independent of that PR.test: make codex-runtime, client-connect and loopback-listener tests …
lidge-jun commentedon Oct 24, 2026
Fixed on dev by #7552 (43f872f): the codex-runtime test now uses an isolated runtime fixture, so it no longer depends on the host's installed Codex. This ships in the next release after 2.92.0. Please reopen if it recurs.