Every pull request waits for the two Windows Build & Test legs. On run 36757693602 they took 31.5 and 30.6 minutes (28.4 and 27.8 of them running tests), while every other job took 1–9 minutes. Earlier Windows legs have also hit the 40-minute timeout.
The same tests take about four times as long on Windows (1556 s against 373 s of test time). Most of the gap is in tests that create a temp folder and a SQLite database per test (tests/core: 497 s against 44 s). On the Windows runner those temp folders are on C:, while the workspace and runner.temp are on D:.
The workflow also runs lint twice per leg and runs the full suite a second time for the coverage floor and for the packaged dashboard e2e.
Expected: pull request feedback limited by the actual work, with every OS/Node combination still running the full suite.
Every pull request waits for the two Windows Build & Test legs. On run 36757693602 they took 31.5 and 30.6 minutes (28.4 and 27.8 of them running tests), while every other job took 1–9 minutes. Earlier Windows legs have also hit the 40-minute timeout.
The same tests take about four times as long on Windows (1556 s against 373 s of test time). Most of the gap is in tests that create a temp folder and a SQLite database per test (
tests/core: 497 s against 44 s). On the Windows runner those temp folders are onC:, while the workspace andrunner.tempare onD:.The workflow also runs lint twice per leg and runs the full suite a second time for the coverage floor and for the packaged dashboard e2e.
Expected: pull request feedback limited by the actual work, with every OS/Node combination still running the full suite.