Abort test requires a sandbox-independent execution fixture
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What is happening?
The focused codex-core abort test can fail when the test runner cannot create its sandbox namespace. In that case, the shell process never reaches the interruption path; the test records the sandbox startup error instead of an aborted command.
Expected behavior
The test should exercise interruption and verify the elapsed-time output independently of whether the runner provides the default sandbox implementation.
Verification
Commit 9ec70ca31c adds a test-only full-access execution fixture for the abort tests. The existing elapsed-time assertion then passes without changing production behavior or the model tool-call payload. An upstream implementation should provide an explicit execution fixture or equivalent test isolation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the focused codex-core abort test and reproduce the failure when the runner cannot create its sandbox namespace. Review commit 9ec70ca31c for the test-only execution-fixture direction. Done means the test reaches the interruption path and its elapsed-time assertion passes without production or model tool-call changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100