Skip to content

CI: split CPU build and tests into parallel jobs - #120

Merged
phantoslayer21 merged 2 commits into
mainfrom
ci-split-cpu-jobs
Nov 14, 2026
Merged

phantoslayer21 merged 2 commits into
mainfrom
ci-split-cpu-jobs

Conversation

@phantoslayer21

@phantoslayer21 phantoslayer21 commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

The single "CPU build and tests" job (about 27 minutes on main) becomes parallel jobs. No test is dropped; the steps are
the same commands, moved into jobs.

Jobs

Job What runs (same commands as before)
CPU: converter and shared settings converter build + ctest (out/converter); wgshared build + ctest (out/wgshared)
CPU: FSR front end front end build + ctest -R "unit|hosted|diagnostic|support" -E "overlay|split|d3d12"
CPU: launcher mock HIP runtime; launcher core targets + ctest -R "^(wg-core|launcher-core|coexist-core|convert-ignore|source-size|wording)$"
CPU: Ray Reconstruction plugin build.py --no-tests (with its WARP probe/hook tests), run_proxy_core_tests.py, then run_python_tests.py --group proxy (test_optimal.py, the one Python module that reads the plugin build)
CPU: Python tests 1/3, 2/3, 3/3 run_python_tests.py --jobs 3 --shard K/3: every other Python module; test_stages.py (812 s) split by test id into six lists
CPU build and tests runs after all of the above; passes only if every one of them passed
  • Required check: the final job keeps the name CPU build and tests, so branch protection and open PRs need no
    change. "Licence and line endings" is unchanged.
  • No build output is shared between jobs; each job builds what it needs. The Python shards keep the old step's
    environment (MSVC developer prompt, numpy, ninja). Grep shows that the only Python module reading the plugin build
    (WG_RR_PROXY_BUILD) is test_optimal.py, which now runs in the plugin job, so it isn't skipped. No module reads
    the mock HIP runtime or another job's out/ folder.
  • run_python_tests.py without options runs the whole set as before. In shard mode every shard computes the whole
    plan and stops if any module (or test id of a split module) is missing or in two parts; --plan 3 prints it.

Totals: old single job against the new jobs

Old: run 43531456640 (main 2085f40, the last green single job). New: this PR's run 43539004405 (base main cdee313).

Job ctest Plugin CPU tests Python modules Python ran / skipped
converter and shared settings converter 4/4, wgshared 4/4
FSR front end 15/15 (1 skipped: fsr_asi_scan_unit, as before)
launcher 6/6
Ray Reconstruction plugin 5 run, 0 failed 1 (test_optimal.py) 4 / 0
Python tests 1/3 31 250 / 23
Python tests 2/3 31 (incl. test_stages.py parts) 205 / 45
Python tests 3/3 32 (incl. test_stages.py parts) 249 / 36
new, all jobs 29 5 93 708 / 104
old single job 28 5 92 703 / 104

Every difference comes from commits merged between 2085f40 and cdee313, not from the split:

  • launcher ctest +1: convert-ignore (added with Converter search: ignore lists for upscaler DLLs another installer placed #46); the other five launcher tests, converter 4, wgshared 4 and
    front end 15 are the same tests.
  • Python +1 module, +5 tests: test_l_runtime_pack.py is new (3 tests); test_l_runtime_load.py has 2 more tests (5 → 7).
    703 + 3 + 2 = 708; skipped 104 = 104.
  • Every other module has the same ran / skipped counts as in the old job (checked module by module), including
    test_stages.py: 36 tests = six parts of 6 across shards 2 and 3, and test_optimal.py: 4 ran, 0 skipped, in the
    plugin job.

Wall time

Wall time
old: "CPU build and tests" (one job) 26 min 40 s (Python tests 17 min 23 s, RR plugin 4 min 26 s, converter 1 min 57 s, launcher 1 min 8 s, front end 1 min 4 s)
new: slowest job (Python tests 1/3) 4 min 47 s
new: other jobs Python 3/3 4:46, Python 2/3 4:26, RR plugin 3:32, launcher 3:11, converter + shared 2:51, front end 1:10, final check 0:04
new: whole run, start to last job 4 min 58 s

The jobs ran at the same time on GitHub-hosted runners; queue time isn't counted.

The single CPU job (about 27 minutes, 17 of them the Python test set) becomes parallel jobs: converter and shared
settings; FSR front end; launcher; Ray Reconstruction plugin (with the one Python module that needs its build,
test_optimal.py); the Python test set in three shards. Each job builds what it needs; no build output is shared.
A final job keeps the required check name "CPU build and tests" and passes only when every split job passed.

run_python_tests.py: --shard K/N and --group proxy run parts of the set; without options it runs the whole set as
before. test_stages.py (812 s) is split by test id into six lists. Every shard computes the whole plan and checks
that each module or test id is in exactly one part; --plan N prints it.

Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
@phantoslayer21
phantoslayer21 marked this pull request as ready for review November 14, 2026 01:17
A cancelled run skipped the gate job, and a skipped required check counts as passing. With always() the gate runs
and fails unless every split job reports success.

Signed-off-by: phantoslayer21 <156617979+phantoslayer21@users.noreply.github.com>
@phantoslayer21
phantoslayer21 merged commit 750a530 into main Nov 14, 2026
9 checks passed
@phantoslayer21
phantoslayer21 deleted the ci-split-cpu-jobs branch November 14, 2026 01:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant