remote-tests

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
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.
部分Codex集成测试支持针对远程执行器运行。 这意味着当设置了CODEX_TEST_REMOTE_ENV环境变量时,测试会尝试在该变量指向的Docker容器中启动一个执行器进程,并将其用于测试。
Docker容器通过./scripts/test-remote-env.sh脚本构建和初始化。
目前仅Linux系统支持运行远程测试,因此你需要使用devbox来运行它们。
你可以通过
applied_devbox ls
命令列出devbox,选择名称中包含
codex
的那一个。 通过
ssh <devbox_name>
连接到devbox。 复用
~/code/codex
中已有的Codex代码副本。如有需要,重置文件。多个代码副本会增加构建时间并占用更多空间。 检查远程端和本地端的SHA值及修改文件是否同步。