Run scenarios in parallel workers on Windows

Aberta
  • Algo errado?
#427 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
bash, php, sqlite
Domínio
ci-cd, testing

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

scope:testing

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 uses TEMP/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.

Linguagem predominante
PHP
Estrelas
42
Forks
28
Merge médio
18h 52min
PRs com merge (30d)
27

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de wp-cli/wp-cli-tests

Todas as issues de wp-cli/wp-cli-tests

Issues semelhantes

Mais issues de PHP

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.