Skip to content

Isolate executable fixture copies in CLI tests on Linux - #48213

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/88f36826bbc6ab4e16e28ff02d5e7d6bd8dbf793
Sep 25, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/88f36826bbc6ab4e16e28ff02d5e7d6bd8dbf793

Conversation

@copyberry

@copyberry copyberry Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Isolate executable fixture copies in CLI tests on Linux

Why

Sibling tests can spawn children while an executable fixture is open for
writing, allowing inherited writable descriptors to cause ETXTBSY when
launching the fixture.

What changed

Add a shared copy_executable helper for the daemon, doctor path safety, and
exec-server tests. On Linux, run /bin/cp in a separate process and wait for
it to exit before launching the fixture, then restore the source permissions
to account for restrictive umasks. Keep std::fs::copy on other platforms.

## Why

Sibling tests can spawn children while an executable fixture is open for
writing, allowing inherited writable descriptors to cause `ETXTBSY` when
launching the fixture.

## What changed

Add a shared `copy_executable` helper for the daemon, doctor path safety, and
exec-server tests. On Linux, run `/bin/cp` in a separate process and wait for
it to exit before launching the fixture, then restore the source permissions
to account for restrictive umasks. Keep `std::fs::copy` on other platforms.

GitOrigin-RevId: 88f36826bbc6ab4e16e28ff02d5e7d6bd8dbf793
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/88f36826bbc6ab4e16e28ff02d5e7d6bd8dbf793 branch from 054923f to 58670ee Compare September 25, 2026 20:54
@copyberry
copyberry Bot merged commit 58670ee into main Sep 25, 2026
18 of 23 checks passed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/88f36826bbc6ab4e16e28ff02d5e7d6bd8dbf793 branch September 25, 2026 20:54
@github-actions github-actions Bot locked and limited conversation to collaborators Sep 25, 2026
@ezoterik
ezoterik deployed to issue-triage September 25, 2026 21:07 — with GitHub Actions Active
@ezoterik
ezoterik deployed to issue-triage September 25, 2026 21:07 — with GitHub Actions Active
@ezoterik
ezoterik deployed to issue-triage September 25, 2026 21:07 — with GitHub Actions Active
@halfdecay
halfdecay deployed to issue-triage September 25, 2026 21:25 — with GitHub Actions Active
@halfdecay
halfdecay deployed to issue-triage September 25, 2026 21:25 — with GitHub Actions Active
@halfdecay
halfdecay deployed to issue-triage September 25, 2026 21:25 — with GitHub Actions Active
@halfdecay
halfdecay deployed to issue-triage September 25, 2026 21:26 — with GitHub Actions Active
@abgri
abgri deployed to issue-triage September 25, 2026 21:42 — with GitHub Actions Active
@abgri
abgri deployed to issue-triage September 25, 2026 21:42 — with GitHub Actions Active
@abgri
abgri deployed to issue-triage September 25, 2026 21:42 — with GitHub Actions Active
@abgri
abgri deployed to issue-triage September 25, 2026 21:43 — with GitHub Actions Active
@nunolu
nunolu deployed to issue-triage September 25, 2026 21:43 — with GitHub Actions Active
@nunolu
nunolu deployed to issue-triage September 25, 2026 21:43 — with GitHub Actions Active
@nunolu
nunolu deployed to issue-triage September 25, 2026 21:43 — with GitHub Actions Active
@nunolu
nunolu deployed to issue-triage September 25, 2026 21:44 — with GitHub Actions Active
@jomero01
jomero01 deployed to issue-triage September 25, 2026 22:05 — with GitHub Actions Active
@jomero01
jomero01 deployed to issue-triage September 25, 2026 22:05 — with GitHub Actions Active
@jomero01
jomero01 deployed to issue-triage September 25, 2026 22:05 — with GitHub Actions Active
@jomero01
jomero01 deployed to issue-triage September 25, 2026 22:06 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
issue-triage — 58670eea Deployed Sep 25, 2026 by jomero01 via Identify potential duplicates (open issues fallback) #48399
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants