Fix Windows baseline test compatibility#401
Merged
Merged
Conversation
This was referenced Jul 7, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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
This PR fixes Windows baseline test compatibility issues without changing live trading, broker, scheduler, shell-tool, or remote API behavior.
The original Windows baseline failed in four concentrated areas:
HOME, while Windows home resolution can still useUSERPROFILE.0700permissions, which are not directly round-trippable on Windows ACL-based filesystems.spawn.502 Bad Gatewayresponses.Changes
Added an explicit loader cache root override for tests while preserving the production default cache path.
Made OAuth token cache permission assertions platform-aware:
0700.Skipped the fork-dependent parallel bench mock test on Windows only.
Updated MCP loopback fixture setup so local
127.0.0.1/localhosttraffic bypasses environment proxies during the fixture lifecycle.Validation
Validated on Windows PowerShell with Python 3.12.12 in an isolated virtual environment.
Targeted tests:
Full baseline:
CLI check:
Safety Notes
This PR does not:
serveVIBE_TRADING_ENABLE_SHELL_TOOLSagent/.env