Skip to content

test: make proxy readiness deterministic on Windows - #132

Merged
RobLe3 merged 1 commit into
mainfrom
codex/windows-proxy-e2e-readiness
Sep 4, 2026
Merged

RobLe3 merged 1 commit into
mainfrom
codex/windows-proxy-e2e-readiness

Conversation

@RobLe3

@RobLe3 RobLe3 commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • use an explicit no-proxy opener for the loopback-only real-proxy test;
  • preserve the minimal test environment while supplying required Windows process variables;
  • stop the readiness loop when the child exits.

Evidence

  • uv run --locked --extra dev pytest -q tests/proxy/test_e2e.py — 1 passed
  • uv run --locked --extra dev pytest -q — 1,254 passed, 2 skipped, 9 subtests passed
  • root cross-repository CI preflight selected and passed the Python portable-local lane

The AWS observation was a diagnostic rehearsal and earns no artifact or qualification credit. A later clean immutable Windows run remains required.

Closes #131

@RobLe3
RobLe3 merged commit 5251bb8 into main Sep 4, 2026
1 check passed
@RobLe3
RobLe3 deleted the codex/windows-proxy-e2e-readiness branch September 4, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[pre-1.0][Windows] Make real-proxy readiness deterministic

1 participant