Run scenarios in parallel workers on Windows

Aperta
  • Qualcosa non va?
#427 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, php, sqlite
Ambito
ci-cd, testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

os:windows scope:testing status:unconfirmed

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.

Lingua principale
PHP
Stelle
42
Fork
29
Merge medio
18h 52m
PR unite (30g)
27

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wp-cli/wp-cli-tests

Tutte le issue di wp-cli/wp-cli-tests

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.