mirror of https://github.com/openai/codex.git synced 2026-09-03 14:59:03 +00:00

Files

Adam Perry @ OpenAI f158b31db5 test: generalize exec-server fixture (#31422 )

## Why

Remote-executor integration tests need one host-agnostic exec-server
fixture target instead of a Windows-only wrapper.

## What

- rename the testing binary target to exec-server
- make the fixture source and target host-agnostic
- update Windows remote-executor test wiring to use the shared target

## Validation

- bazel build //codex-rs/exec-server/testing:exec-server
- bazel cquery --config=ci-windows-cross
'set(//codex-rs/exec-server/testing:exec-server
//codex-rs/core/tests/remote_env_windows:smoke-test)'

## Stack

1. [#31422 test: generalize exec-server
fixture](https://github.com/openai/codex/pull/31422)
2. [#31425 test: add TestAppServer
builder](https://github.com/openai/codex/pull/31425)
3. [#31427 test: add delayed exec-server
transport](https://github.com/openai/codex/pull/31427)
4. [#31295 bench: add cold skill load
macrobenchmark](https://github.com/openai/codex/pull/31295)
5. [#31428 bench: add e2e benchmark
entrypoints](https://github.com/openai/codex/pull/31428)
6. [#31429 ci: smoke Bazel e2e
benchmarks](https://github.com/openai/codex/pull/31429)

2026-07-07 11:21:56 -07:00

BUILD.bazel

test: generalize exec-server fixture (#31422 )

2026-07-07 11:21:56 -07:00

README.md

Run core integration tests against a Wine-backed Windows executor (#28401 )

2026-06-16 00:38:41 +00:00

remote_env_windows_test.rs

app-server: cover selected environments in integration tests (#29992 )

2026-07-07 00:42:43 +00:00

README.md

Windows remote-environment test

This Bazel-only test_codex integration test runs a Windows exec-server fixture under pinned Wine and exercises the normal model tool-call and remote-execution path.

Running the test

bazel test \
  //codex-rs/core/tests/remote_env_windows:smoke-test \
  --test_output=errors

No system Wine is required. Every process gets a fresh WINEPREFIX and isolated wineserver.

Current limitations

ConPTY/TTY behavior is not yet covered.
Wine loads shared objects and PE DLLs at runtime, so the host must still provide the declared compatible glibc version.
The target is intentionally limited to x86-64 for simplicity. It can expand if we find aarch64-specific behavior worth testing.