[codex] fix builtin MCP Windows path test#21350
Merged
Merged
Conversation
Co-authored-by: Codex <noreply@openai.com>
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.
1 participant
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.
Summary
--codex-homeargument fromAbsolutePathBufWhy
AbsolutePathBuf::try_from("/tmp/codex-home")is rendered asD:\\tmp\\codex-homeon Windows, but the test asserted the Unix literal"/tmp/codex-home". That made the Windows Bazel job fail even though the production code was behaving correctly.Impact
This keeps the test cross-platform while preserving the same transport assertion on Unix and Windows.
Validation
cargo test -p codex-builtin-mcps