Run scenarios in parallel workers on Windows
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 25/100
调研方向
Start with the Windows branch in bin/run-behat-tests, which sets PARALLEL to empty, and with the worker startup, output and exit-code handling in utils/behat-parallel.php. Check how temporary directories and TMPDIR/TEMP are used under Git Bash. Done means the Windows job runs with WP_CLI_TEST_PARALLEL=4 on a draft branch, with results matching the serial run and Behat time reduced. This needs Windows CI access and familiarity with the project's process handling.
由索引模型根据 Issue 内容生成。
描述
Part of #394. Follow-up to #390.
bin/run-behat-tests turns parallel workers off on Windows (MINGW*|MSYS*|CYGWIN*) PARALLEL="";;), and the Docker mode is unavailable there as well, so the Windows Behat job runs every scenario one after the other. Since the Linux jobs run in 4 parallel workers, the Windows job is now the longest job of most large suites. In the full-matrix runs of 2026-11-02:
| Package | Longest Linux job | macOS job (4 workers) | Windows job (serial) |
|---|---|---|---|
entity-command |
9.8 min | 23.2 min | 53.0 min |
extension-command |
8.4 min | 12.9 min | 28.7 min |
core-command |
5.3 min | 4.7 min | 11.4 min |
media-command |
4.9 min | 6.9 min | 11.0 min |
scaffold-command |
5.4 min | 3.4 min | 9.1 min |
language-command |
4.4 min | 3.4 min | 8.8 min |
The Windows job is continue-on-error, so it does not block a pull request. It still sets how long the Testing workflow takes to finish, though. In entity-command, the job took 53 minutes for 498 scenarios. The macOS job already runs in parallel workers on the runner and went from about 26 to 23 minutes.
The Windows job uses SQLite, so the worker databases are not an obstacle. #405 does not say why Windows was left out. Things to check before turning it on:
- process handling in
utils/behat-parallel.php(starting the workers, collecting their output and exit codes, and signals, see #418) with Git Bash and the Windows PHP build; - per-worker temporary directories and
TMPDIR, as Windows usesTEMP/TMP, and the runner moves temporary files to the D: drive; - run directories are still removed right away on Windows (#403), which may make workers slower than expected;
- scenarios that use fixed ports or background processes, which already run in the first worker.
Measuring: run the Windows job of entity-command and extension-command with WP_CLI_TEST_PARALLEL=4 on a draft branch, and compare Behat time and results with the serial runs of 2026-11-02. Check the first parallel pass, not only the result after composer behat-rerun.
- 主要语言
- PHP
- 星标
- 42
- 派生
- 28
- 平均合并
- 18 小时 52 分钟
- 30 天内合并 PR
- 27
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
wp-cli/wp-cli-tests 的其他 Issue
-
scope:testing status:unconfirmed
难度 2/5 1-3 小时 新手友好度 65/100
wp-cli/wp-cli-tests#389 · 1 条评论 ·
维护者通常 1 天内回复
-
scope:testing
难度 4/5 3-5 天 新手友好度 22/100
wp-cli/wp-cli-tests#426 ·
维护者通常 1 天内回复
-
scope:testing
难度 4/5 3-5 天 新手友好度 25/100
wp-cli/wp-cli-tests#425 ·
维护者通常 1 天内回复
-
scope:testing
难度 5/5 一周以上 新手友好度 20/100
wp-cli/wp-cli-tests#395 ·
维护者通常 1 天内回复
-
scope:testing
难度 4/5 3-5 天 新手友好度 30/100
wp-cli/wp-cli-tests#394 ·
维护者通常 1 天内回复
查看 wp-cli/wp-cli-tests 的全部 Issue
相似的 Issue
-
Recognise PHP_CodeSniffer (`phpcs`) as a linter可能已有人在做 @HarshRajSinghania 今天认领。 未关闭enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
MustacheCase/zanadir#507 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
jwage/phpamqplib-messenger#163 ·
-
Newsletter subscription page logs Undefined array key "nw_error" on every GET可能已有人在做 @Codencode 今天认领。 未关闭
难度 1/5 1-3 小时 新手友好度 82/100
PrestaShop/ps_emailsubscription#145 · 1 条评论 ·
-
难度 1/5 1 小时以内 新手友好度 82/100