Conversation
dylan-hurd-oai
approved these changes
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A Windows Cargo build on
maintimed out in several unrelated-looking suites at the same time:codex-app-serveraccount tests failed before account logic, whilemcp.initialize()was waiting for the first JSON-RPC response.codex-coreapply_patch_clitests timed out while running full Codex/apply_patch turns.codex-windows-sandboxlegacy session tests timed out while creating restricted-token child processes and private desktops.The app-server log reached the test harness write path in
McpProcess::initialize_with_params, but never printed the matching stdout read fromread_jsonrpc_message. The server initialize handler is a small bookkeeping/response path (message_processor.rs), so the failure looks like Windows runner process/pipe scheduling starvation rather than account-specific behavior.What Changed
This updates
.config/nextest.tomlto serialize two process-heavy sets:codex-coretests matchingpackage(codex-core) & kind(test) & test(apply_patch_cli)codex-windows-sandboxtests matchingpackage(codex-windows-sandbox) & test(legacy_)codex-app-serverintegration tests were already serialized inside their own package; this change reduces overlap with the other suites that were saturating the runner at the same time.Verification
cargo nextest list --filterset "package(codex-core) & kind(test) & test(apply_patch_cli)"cargo nextest list --filterset "package(codex-windows-sandbox) & test(legacy_)"The Windows sandbox filter naturally lists no tests on macOS, but it validates the nextest filter/config syntax locally.