82f3140847
Complete architecture document set with multi-model review remediation: - Frozen interface contracts, runtime semantics, DB schemas - Event/tool/error/provider registries - Scheduler and main agent state machines - C4 module/code views, solution architecture, baseline V1 - Multi-model review reports and joint assessment - Phase-gate remediation complete (P0/P1/P2/UX resolved) - Implementation plan with T-000A through T-045 - Reference folders kept as placeholders only
17 lines
872 B
Markdown
17 lines
872 B
Markdown
---
|
|
name: remote-tests
|
|
description: How to run tests using remote executor.
|
|
---
|
|
|
|
Some codex integration tests support a running against a remote executor.
|
|
This means that when CODEX_TEST_REMOTE_ENV environment variable is set they will attempt to start an executor process in a docker container CODEX_TEST_REMOTE_ENV points to and use it in tests.
|
|
|
|
Docker container is built and initialized via ./scripts/test-remote-env.sh
|
|
|
|
Currently running remote tests is only supported on Linux, so you need to use a devbox to run them
|
|
|
|
You can list devboxes via `applied_devbox ls`, pick the one with `codex` in the name.
|
|
Connect to devbox via `ssh <devbox_name>`.
|
|
Reuse the same checkout of codex in `~/code/codex`. Reset files if needed. Multiple checkouts take longer to build and take up more space.
|
|
Check whether the SHA and modified files are in sync between remote and local.
|