openai/codex
1
0
Fork 0
mirror of https://github.com/openai/codex.git synced 2026-10-29 19:08:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

Record validation pass 3

Browse Source 
Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
Ahmed Ibrahim
2026-03-17 05:51:39 +00:00
co-authored by Codex
parent e1e205c2df
commit 7814705a19
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/flaky-test-triage.md
+2
View File
@@ -83,6 +83,7 @@ Older failures also appeared on Linux, but the repeated cross-PR signal is stron
- Current follow-up: make the worker emit an internal `started` message and arm the initial yield timer only after that signal arrives, so `yield_time_ms` measures script execution time instead of worker startup delay.
- Runs `23178075559` (`rust-ci`) and `23178075565` (`Bazel (experimental)`) finished green on head `d8450f8e2`. The code-mode runner now starts the initial yield timer only after the worker signals that execution has started, so `code_mode_yield_timeout_works_for_busy_loop` no longer races against worker startup latency. This is pass 1 of 5 after the latest failing run.
- Runs `23179196582` (`rust-ci`) and `23179196522` (`Bazel (experimental)`) finished green on doc-only head `ad5be933d`, including the long-running Windows x64 and Windows arm64 `Tests` shards. That makes the current validation streak 2 of 5 after the latest failure.
- Runs `23179852430` (`rust-ci`) and `23179852450` (`Bazel (experimental)`) finished green on doc-only head `e1e205c2d`, again including both Windows `Tests` shards. That extends the current validation streak to 3 of 5 after the latest failure.
- Rationale: these failures are test-harness flakes, not product behaviors. The fixes keep the assertions intact and remove environment-sensitive startup and ordering hazards instead of stretching timeouts.
## Constraints
@@ -129,3 +130,4 @@ Older failures also appeared on Linux, but the repeated cross-PR signal is stron
| `65f7f64ae` | Record validation pass 1 | failed | Run `23177624353` failed only in `Tests — ubuntu-24.04 - x86_64-unknown-linux-gnu`, in `codex-core::all::suite::code_mode::code_mode_yield_timeout_works_for_busy_loop`, while `Bazel (experimental)` run `23177624352` finished green on the same head. The only diff from the prior full-green head `4a3181290` was one extra line in this tracking document, so the failure exposed a latent code-mode yield race: the runner started the initial `yield_time_ms` timer when the worker was created, allowing the `100ms` budget to expire before the worker began executing user code on a loaded CI machine. |
| `d8450f8e2` | Fix code mode yield startup race | full pass | Runs `23178075559` (`rust-ci`) and `23178075565` (`Bazel (experimental)`) both finished green for the full PR, including the previously flaky `Tests — ubuntu-24.04 - x86_64-unknown-linux-gnu` shard and both Windows `Tests` jobs. The code-mode runner now starts the initial yield timer only after the worker signals that execution has started, so `yield_time_ms` measures script runtime rather than worker startup latency. This is pass 1 of 5 after the latest failing run. |
| `ad5be933d` | Record validation pass 1 | full pass | Runs `23179196582` (`rust-ci`) and `23179196522` (`Bazel (experimental)`) finished green for the full PR, including the long-running Windows x64 and Windows arm64 `Tests` jobs. This extends the current streak to 2 consecutive full-suite green commits after `d8450f8e2`. |
| `e1e205c2d` | Record validation pass 2 | full pass | Runs `23179852430` (`rust-ci`) and `23179852450` (`Bazel (experimental)`) finished green for the full PR, including both Windows `Tests` jobs. This extends the current streak to 3 consecutive full-suite green commits after `d8450f8e2`. |