WIP: test: pytest runs the game-free checks; requirements by machine; main's known failures #1818

Draft
dyst wants to merge 3 commits from dyst/Longshot:test/pytest-runner into main
Member

Type: test · Risk: low · Tested on: Windows 11, Ryzen 9 3900X (game-free checks only) · Needs: Linux

TL;DR

Our game-free checks are 860 separate scripts with no test library: a check that cannot run on a PC prints "skipped" and counts as passed, the runner takes whatever compiler is first on PATH (on Windows often an old gcc that fails checks the game's own compiler passes), and main always shows about 45 failures, so a new one is easy to miss. This PR lets pytest run every check unchanged, picks the Builder's compiler, skips a check the machine cannot run with the reason, and lists main's known failures so a red run means something new broke. On Windows, main went from 87 failures to 38 known ones and none new.

Breakdown

  • Who it helps: everyone who runs the checks before a pull request, and reviewers who read the results.
  • What was wrong: checks guarded only by OS, a skip counted as a pass, the compiler was the first on PATH, and main's own failures hid new ones.
  • What changes: pytest runs the same checks (run_all.py still does too), checks can declare the CPU, compiler and flags they need, the Builder's llvm-mingw is the default compiler, and tests/known_failures.txt lists main's failures.
  • What does not change: no existing check had to be rewritten; CI and mise run test still call run_all.py with the same flags; nothing in the game.
  • How it was checked: full runs of main and this branch under both runners on Windows; the runners' own tests, including a new pytest module that runs both runners end to end.
  • What is still open: a Linux run (the Linux entries of the known failures list are empty until one is made), and the 51 other checks that still print "skipped" and exit 0.
  • Risk: low: tests and docs only; the visible change is a different default compiler for the checks on Windows.

Why

The checks are the only safety net we have (Forgejo runs none and CircleCI has been stuck since Nov 15, #1412), and today their results can't be trusted at a glance:

  • A skip counts as a pass. 52 checks print "skipped" and exit 0 when they can't run on a PC (another CPU, no compiler); the table shows them as passed.
  • Only the OS can be declared. RUN_ALL_SKIP is by OS; 16 checks build with -march, AVX or intrinsics and only 9 of them look at the CPU first.
  • The compiler is the first on PATH. On this PC that is an old TDM gcc 10.3: 87 failures on main, against 38 with the Builder's llvm-mingw, and last week it hid a real regression behind about 30 false failures.
  • Main is always red. About 45 checks fail on a clean main, so each author compares their failures with a list kept by hand.

The longer plan is for features to move into folders of their own with their tests beside them (gpu/vk/menu/ since #1774); pytest finds a feature's tests/ there.

What changed

pytest runs every check tests/run_all.py runs, without a check changing: a test file that imports pytest is a pytest module, every other one a script check run in its own process exactly as run_all runs it. What both runners need from the machine is in one place, tests/check_env.py.

  • pytest: tests/pytest_longshot.py (the plugin: how a script check and a pytest module are run, the requires marker, the fixtures cxx, compile_cxx, read_source, machine, repo), the root conftest.py and pytest.ini (tests/, nx2/ and the tests/ of gpu/ and host/). tests/requirements.txt pins pytest 9.2.0, pytest-xdist 3.8.0 and pytest-timeout 2.4.0; mise run test-deps, mise run pytest. run_all itself still needs no package.
  • The compiler: check_env.find_toolchain(): $CXX, then LONGSHOT_MINGW's clang++, then the Builder's own llvm-mingw (scripts/dev_build.py's builder folder), then PATH. An llvm-mingw it picks goes first on PATH (its programs load its libc++ DLLs from there) and becomes LONGSHOT_MINGW when that is unset (the a64-kit's extension builds through it; without it six checks stopped on 'algorithm' file not found). Every run's first line says what it found: here: windows x86_64 x86-64-v3, clang 23.1 (mingw) at ....
  • Requirements: RUN_ALL_REQUIRES = {...} in a script check, @pytest.mark.requires(...) on a pytest test: os, arch, cpu (features or a level, x86-64-v3), cxx (clang>=17, gcc>=13) and cxx_flags. A machine that lacks an OS, CPU or feature always skips (even when the check is named; --no-skip still runs it); a missing or too old compiler skips, or fails with --strict. CPU features come from a small CPUID and XGETBV program (any gcc or clang) or /proc/cpuinfo.
  • Skips: check_env.skip(why) ends a script check with exit 77, shown as skipped with the reason. tests/test_fastfp_fma.py is converted as the example.
  • Known failures: tests/known_failures.txt, one line a check: <check> <os> <why>. Listed and failing: known, not a failure of the run. Listed and passing: FIXED, a failure until its line goes. A pytest module's entries are applied by pytest as strict xfails (by file or by node id).
  • run_all.py: reads RUN_ALL_REQUIRES, runs a pytest module with python -m pytest, honours exit 77 and the known failures, prints the machine, and looks up each tool once (which() cached: collection went from 18 s to 10 s under pytest).
  • Two checks this exposed: tests/test_game_menu_mouse_buttons.py's fixture kept three counters nothing read, which clang 21+ refuses under -Werror (its own commit). tests/test_vbytes.py, which never ran on Windows before, would take about 25 minutes there (6 minutes a -march; stopped after 22) at its default 1,000,000 random states per guest word (130 words, four -march builds): the runners now pass --random 50000, which still gives every index value of every word about 3,000 hits (its own commit, with the reasoning; for #1576's author: a full-depth run is still python -I -B tests/test_vbytes.py, and a stronger check would feed every one of the 256 index values to every lane).
  • Docs: CONTRIBUTING.md's Testing section and "When you add a fix or a check": new checks as pytest modules with the marker, the known failures, the compiler.
  • The runners' own tests: tests/test_check_env.py (the first pytest module, 33 tests: requirements, the machine, the known failures file, and both runners end to end over a scratch repository); test_run_all_declarations.py covers the new declaration; test_run_all_output.py and test_run_all_reap.py copy check_env.py beside run_all.py.

Measurements

Verdict: on Windows, main's 87 failures under the old runner become 38 known failures and 0 new ones under run_all; pytest agrees on every check but two timeouts under load (below).

Hardware: Windows 11 Pro, Ryzen 9 3900X (x86-64-v3, no AVX-512), Python 3.11.8 in a venv with the repository's pins (numpy 2.4.6: 2.5.4 needs Python 3.12)
Method: a full run of each, 24 at once, one after another (the last pytest run overlapped another session's runtime build)

Before: main @ a433db32, old run_all After: this PR @ 8ffe5053, run_all After: this PR @ 8ffe5053, pytest -n 24
passed 638 720 750
failed 87 0 2 (timeouts under load: below)
known 38 38 (xfailed)
skipped 141 118 118
wall time 978 s 353 s 443 s

(main's 978 s was with the old gcc and other work on the PC: not a speed comparison. pytest counts the 33 tests of test_check_env.py one by one, run_all as one check.)

Of main's 87: 50 pass here (the compiler and LONGSHOT_MINGW failed them, not the code; one more after its fixture fix, and test_vbytes at its runner depth), and 37 are the known failures, each with why. The "Before" column is main @ a433db32; this PR was rebased on 0de25c3e (#1774) since, and both full runs of the rebased branch are the "After" columns.

The 2 pytest failures were timeouts inside the checks while another runtime build ran on this PC (the CPU at 99 %): test_fallback_buffer_cleanup (a 10 s limit on its fixture) and test_jobs_wait_runs_queued (60 s on its race case). Both passed in the run_all run of the same commit, three times each alone under pytest (5 to 7 s), and both were among main's 87: timing-sensitive checks, not this PR. One check that was skipped before (no clang on PATH), test_linux_preflight, now runs and fails as it does wherever clang is found: it is in the list.

Flags and settings

None for the game. For the checks: RUN_ALL_REQUIRES (a declaration), and pytest's --strict-tools, --no-skip, --check-timeout, --skip-exit, --known-exit (the last two are how run_all runs a pytest module).

Testing

Tested: full runs on Windows 11 (Ryzen 9 3900X) of main and of this branch, under run_all.py and under pytest with xdist: the same failures, all in the known list; the runners' own tests pass (test_check_env, test_run_all_declarations, _output, _junit, _changed, _schedule, _reap); test_vbytes and test_seed_reader timed alone.

Not tested: Linux (no Linux PC here): the run_all and pytest paths are the same code, the Linux process reaping is unchanged, and /proc/cpuinfo gives the CPU features there.

Must be tested:

  • Linux, any distribution with clang or gcc: python -I -B tests/run_all.py and python -I -B -m pytest -n auto after python -m pip install -r tests/requirements.txt, expecting the same failures under both; the failing checks go into tests/known_failures.txt as linux lines (by hand: anyone on Linux).

Risks

What could break: on Windows the checks get the Builder's llvm-mingw where it is unpacked, not the first compiler on PATH; a check that only passed with another compiler shows up (test_game_menu_mouse_buttons was one, fixed here). tests/test_seed_reader.py writes its seed file 20,000 times and takes 99 s alone on Windows, near its own 300 s limit under a full parallel run: it timed out in one of the six full runs of this branch here, and failed on main under the old runner (not changed by this PR).

Turning it off: CXX=<compiler> picks another compiler; reverting the commits removes the rest.

Compatibility: nothing changes for a player.

Issues

See #1412 (CI not running).

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Docs updated.

🤖 Generated with Claude Code

**Type:** test · **Risk:** low · **Tested on:** Windows 11, Ryzen 9 3900X (game-free checks only) · **Needs:** Linux ## TL;DR Our game-free checks are 860 separate scripts with no test library: a check that cannot run on a PC prints "skipped" and counts as passed, the runner takes whatever compiler is first on PATH (on Windows often an old gcc that fails checks the game's own compiler passes), and main always shows about 45 failures, so a new one is easy to miss. This PR lets pytest run every check unchanged, picks the Builder's compiler, skips a check the machine cannot run with the reason, and lists main's known failures so a red run means something new broke. On Windows, main went from 87 failures to 38 known ones and none new. ## Breakdown - **Who it helps:** everyone who runs the checks before a pull request, and reviewers who read the results. - **What was wrong:** checks guarded only by OS, a skip counted as a pass, the compiler was the first on PATH, and main's own failures hid new ones. - **What changes:** pytest runs the same checks (run_all.py still does too), checks can declare the CPU, compiler and flags they need, the Builder's llvm-mingw is the default compiler, and `tests/known_failures.txt` lists main's failures. - **What does not change:** no existing check had to be rewritten; CI and `mise run test` still call run_all.py with the same flags; nothing in the game. - **How it was checked:** full runs of main and this branch under both runners on Windows; the runners' own tests, including a new pytest module that runs both runners end to end. - **What is still open:** a Linux run (the Linux entries of the known failures list are empty until one is made), and the 51 other checks that still print "skipped" and exit 0. - **Risk:** low: tests and docs only; the visible change is a different default compiler for the checks on Windows. ## Why The checks are the only safety net we have (Forgejo runs none and CircleCI has been stuck since Nov 15, #1412), and today their results can't be trusted at a glance: - **A skip counts as a pass.** 52 checks print "skipped" and exit 0 when they can't run on a PC (another CPU, no compiler); the table shows them as passed. - **Only the OS can be declared.** `RUN_ALL_SKIP` is by OS; 16 checks build with `-march`, AVX or intrinsics and only 9 of them look at the CPU first. - **The compiler is the first on PATH.** On this PC that is an old TDM gcc 10.3: 87 failures on main, against 38 with the Builder's llvm-mingw, and last week it hid a real regression behind about 30 false failures. - **Main is always red.** About 45 checks fail on a clean main, so each author compares their failures with a list kept by hand. The longer plan is for features to move into folders of their own with their tests beside them (`gpu/vk/menu/` since #1774); pytest finds a feature's `tests/` there. ## What changed pytest runs every check `tests/run_all.py` runs, without a check changing: a test file that imports pytest is a pytest module, every other one a script check run in its own process exactly as run_all runs it. What both runners need from the machine is in one place, `tests/check_env.py`. - **pytest:** `tests/pytest_longshot.py` (the plugin: how a script check and a pytest module are run, the requires marker, the fixtures `cxx`, `compile_cxx`, `read_source`, `machine`, `repo`), the root `conftest.py` and `pytest.ini` (tests/, nx2/ and the tests/ of gpu/ and host/). `tests/requirements.txt` pins pytest 9.2.0, pytest-xdist 3.8.0 and pytest-timeout 2.4.0; `mise run test-deps`, `mise run pytest`. run_all itself still needs no package. - **The compiler:** `check_env.find_toolchain()`: `$CXX`, then `LONGSHOT_MINGW`'s clang++, then the Builder's own llvm-mingw (`scripts/dev_build.py`'s builder folder), then PATH. An llvm-mingw it picks goes first on PATH (its programs load its libc++ DLLs from there) and becomes `LONGSHOT_MINGW` when that is unset (the a64-kit's extension builds through it; without it six checks stopped on `'algorithm' file not found`). Every run's first line says what it found: `here: windows x86_64 x86-64-v3, clang 23.1 (mingw) at ...`. - **Requirements:** `RUN_ALL_REQUIRES = {...}` in a script check, `@pytest.mark.requires(...)` on a pytest test: `os`, `arch`, `cpu` (features or a level, `x86-64-v3`), `cxx` (`clang>=17`, `gcc>=13`) and `cxx_flags`. A machine that lacks an OS, CPU or feature always skips (even when the check is named; `--no-skip` still runs it); a missing or too old compiler skips, or fails with `--strict`. CPU features come from a small CPUID and XGETBV program (any gcc or clang) or `/proc/cpuinfo`. - **Skips:** `check_env.skip(why)` ends a script check with exit 77, shown as skipped with the reason. `tests/test_fastfp_fma.py` is converted as the example. - **Known failures:** `tests/known_failures.txt`, one line a check: `<check> <os> <why>`. Listed and failing: `known`, not a failure of the run. Listed and passing: `FIXED`, a failure until its line goes. A pytest module's entries are applied by pytest as strict xfails (by file or by node id). - **run_all.py:** reads `RUN_ALL_REQUIRES`, runs a pytest module with `python -m pytest`, honours exit 77 and the known failures, prints the machine, and looks up each tool once (`which()` cached: collection went from 18 s to 10 s under pytest). - **Two checks this exposed:** `tests/test_game_menu_mouse_buttons.py`'s fixture kept three counters nothing read, which clang 21+ refuses under `-Werror` (its own commit). `tests/test_vbytes.py`, which never ran on Windows before, would take about 25 minutes there (6 minutes a `-march`; stopped after 22) at its default 1,000,000 random states per guest word (130 words, four `-march` builds): the runners now pass `--random 50000`, which still gives every index value of every word about 3,000 hits (its own commit, with the reasoning; for #1576's author: a full-depth run is still `python -I -B tests/test_vbytes.py`, and a stronger check would feed every one of the 256 index values to every lane). - **Docs:** CONTRIBUTING.md's Testing section and "When you add a fix or a check": new checks as pytest modules with the marker, the known failures, the compiler. - **The runners' own tests:** `tests/test_check_env.py` (the first pytest module, 33 tests: requirements, the machine, the known failures file, and both runners end to end over a scratch repository); `test_run_all_declarations.py` covers the new declaration; `test_run_all_output.py` and `test_run_all_reap.py` copy `check_env.py` beside run_all.py. ## Measurements **Verdict:** on Windows, main's 87 failures under the old runner become 38 known failures and 0 new ones under run_all; pytest agrees on every check but two timeouts under load (below). Hardware: Windows 11 Pro, Ryzen 9 3900X (x86-64-v3, no AVX-512), Python 3.11.8 in a venv with the repository's pins (numpy 2.4.6: 2.5.4 needs Python 3.12) Method: a full run of each, 24 at once, one after another (the last pytest run overlapped another session's runtime build) | | Before: main @ a433db32, old run_all | After: this PR @ 8ffe5053, run_all | After: this PR @ 8ffe5053, pytest -n 24 | |---|---|---|---| | passed | 638 | 720 | 750 | | failed | 87 | 0 | 2 (timeouts under load: below) | | known | | 38 | 38 (xfailed) | | skipped | 141 | 118 | 118 | | wall time | 978 s | 353 s | 443 s | (main's 978 s was with the old gcc and other work on the PC: not a speed comparison. pytest counts the 33 tests of test_check_env.py one by one, run_all as one check.) Of main's 87: 50 pass here (the compiler and `LONGSHOT_MINGW` failed them, not the code; one more after its fixture fix, and test_vbytes at its runner depth), and 37 are the known failures, each with why. The "Before" column is main @ a433db32; this PR was rebased on 0de25c3e (#1774) since, and both full runs of the rebased branch are the "After" columns. The 2 pytest failures were timeouts inside the checks while another runtime build ran on this PC (the CPU at 99 %): `test_fallback_buffer_cleanup` (a 10 s limit on its fixture) and `test_jobs_wait_runs_queued` (60 s on its race case). Both passed in the run_all run of the same commit, three times each alone under pytest (5 to 7 s), and both were among main's 87: timing-sensitive checks, not this PR. One check that was skipped before (no clang on PATH), `test_linux_preflight`, now runs and fails as it does wherever clang is found: it is in the list. ### Flags and settings None for the game. For the checks: `RUN_ALL_REQUIRES` (a declaration), and pytest's `--strict-tools`, `--no-skip`, `--check-timeout`, `--skip-exit`, `--known-exit` (the last two are how run_all runs a pytest module). ## Testing **Tested:** full runs on Windows 11 (Ryzen 9 3900X) of main and of this branch, under run_all.py and under pytest with xdist: the same failures, all in the known list; the runners' own tests pass (test_check_env, test_run_all_declarations, _output, _junit, _changed, _schedule, _reap); test_vbytes and test_seed_reader timed alone. **Not tested:** Linux (no Linux PC here): the run_all and pytest paths are the same code, the Linux process reaping is unchanged, and `/proc/cpuinfo` gives the CPU features there. **Must be tested:** - Linux, any distribution with clang or gcc: `python -I -B tests/run_all.py` and `python -I -B -m pytest -n auto` after `python -m pip install -r tests/requirements.txt`, expecting the same failures under both; the failing checks go into `tests/known_failures.txt` as `linux` lines (by hand: anyone on Linux). ## Risks **What could break:** on Windows the checks get the Builder's llvm-mingw where it is unpacked, not the first compiler on PATH; a check that only passed with another compiler shows up (`test_game_menu_mouse_buttons` was one, fixed here). `tests/test_seed_reader.py` writes its seed file 20,000 times and takes 99 s alone on Windows, near its own 300 s limit under a full parallel run: it timed out in one of the six full runs of this branch here, and failed on main under the old runner (not changed by this PR). **Turning it off:** `CXX=<compiler>` picks another compiler; reverting the commits removes the rest. **Compatibility:** nothing changes for a player. ## Issues See #1412 (CI not running). ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Its stand-ins counted toggle clears, captures and releases, and nothing
read them: clang 21 and later refuse that under -Werror
(-Wunused-but-set-global), so the check failed with the Builder's
llvm-mingw, whose gcc is clang. Passes with clang 23.1 and gcc 10.3.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
--random counts per guest word, and there are 130 of them: the default
1,000,000 is 130M checks per -march, four times, about 25 minutes on a
Ryzen 9 3900X (6 minutes a -march). TBL and EXT work lane by lane, so
50,000 states give each word 800,000 index bytes, every value 0-255
about 3,000 times and the edge values far more: about 2 minutes. The
check's own default stays 1,000,000 for a run by hand.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
test: pytest runs the game-free checks; requirements by machine; known failures
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Successful in 10s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 16s
8ffe5053e1
pytest collects every check tests/run_all.py runs, unchanged: a test file
that imports pytest is a pytest module, every other one a script check run
in its own process as run_all runs it (tests/pytest_longshot.py, the root
conftest.py and pytest.ini). Feature folders' tests/ are found too.

tests/check_env.py, shared by both runners:
- the C++ compiler is $CXX, then LONGSHOT_MINGW's, then the Builder's own
  llvm-mingw, and only then PATH (which here found an old TDM gcc 10.3);
  its folder goes first on PATH and becomes LONGSHOT_MINGW, so the
  programs it builds find its DLLs and the a64-kit's extension builds;
- requirements by OS, CPU architecture, CPU features or level
  (x86-64-v3), compiler family and version, and flags it must take
  (RUN_ALL_REQUIRES, the requires marker); the features from CPUID and
  XGETBV, or /proc/cpuinfo;
- a check that cannot run here ends with skip(why), exit 77: shown as
  skipped with why, where a print and exit 0 counted as a pass;
- tests/known_failures.txt, main's failures per OS with why: known, not
  a failure of the run; one that passes fails it until its line goes.

run_all runs a pytest module with pytest, prints what it found here, and
reads which() once per name. tests/test_check_env.py covers all of it,
end to end under both runners; test_fastfp_fma declares x86-64-v3.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Member

Possibly related, for context:

  • PR #1032 fix(tests): run_all uses the clone's llvm-mingw folder, as make_game does — Overlapping run_all compiler selection; same compiler-discovery code.
  • issue #394 Proposal: use the release structure we already have (nightly for testing, rc that means frozen) — Calls for automated execution of game-free checks, the broader testing context.
Possibly related, for context: - PR #1032 fix(tests): run_all uses the clone's llvm-mingw folder, as make_game does — Overlapping run_all compiler selection; same compiler-discovery code. - issue #394 Proposal: use the release structure we already have (nightly for testing, rc that means frozen) — Calls for automated execution of game-free checks, the broader testing context.
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Successful in 10s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 16s
This pull request has changes conflicting with the target branch.
  • CONTRIBUTING.md
  • mise.toml
  • tests/run_all.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'test/pytest-runner:dyst-test/pytest-runner'
git switch 'dyst-test/pytest-runner'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1818
No description provided.