mirror of
https://github.com/openai/codex.git
synced 2026-11-06 20:20:34 +00:00
Record validation pass 1
Document the fully green CI result for cc4785e3f and continue the streak toward five consecutive passing commits on this PR.
Co-authored-by: Codex <noreply@openai.com>
This commit is contained in:
@@ -98,3 +98,4 @@ Older failures also appeared on Linux, but the repeated cross-PR signal is stron
|
||||
| `ef5a05fa3` | Inline in-process request response types | failed | Run `23085144063` cleared the private-alias compile break, but every non-release `Lint/Build` target still failed in `cargo clippy` while release builds passed. The next follow-up replaces the inline `IoResult<Result<...>>` signatures with a documented public alias, which is the smallest code change consistent with the cross-target `cargo clippy` pattern. |
|
||||
| `d87051f57` | Factor in-process request response alias | failed | Run `23085369065` narrowed the non-release `cargo clippy` failures down to a single test-harness warning: `unused import: codex_app_server_protocol::JSONRPCErrorError` in `app-server/tests/suite/fuzzy_file_search.rs`. The next follow-up removes that import so the request-order fix can finish the matrix. |
|
||||
| `d4cbc97a9` | Remove unused fuzzy search test import | failed | Run `23085620967` cleared every completed non-release `Lint/Build` lane and passed Bazel after rerunning a flaky macOS x64 shard, but `Tests — ubuntu-24.04-arm - aarch64-unknown-linux-gnu` failed in `all::suite::fuzzy_file_search::test_fuzzy_file_search_session_multiple_query_updates_work`. The failure stack pointed to `wait_for_session_completed`, and the harness was still dropping out-of-order `sessionCompleted` notifications while waiting for matching `sessionUpdated` events. |
|
||||
| `cc4785e3f` | Buffer fuzzy search session notifications | full pass | Runs `23085926272` (`rust-ci`) and `23085926275` (`Bazel (experimental)`) finished green for the full PR after rerunning the two failed Bazel Linux shards on the same SHA. The fuzzy-search harness now buffers unmatched notifications, so out-of-order `sessionCompleted` events no longer disappear before the completion wait starts. This is pass 1 of 5 after the latest failing run. |
|
||||
|
||||
Reference in New Issue
Block a user