build(release): the pipeline tour's list from a tour of main f637b42d, 10993 pipelines #957

Open
jabbaxipil wants to merge 1 commit from jabbaxipil/Longshot:tour-list into main
First-time contributor

Type: build · Risk: low · Tested on: Linux (Ubuntu 26.04.1), RTX 4070 · Needs: none

Why

assets/pipeline_states/tour.bin.xz is still the list from the draft tour (Hookshot's PR 2048) on main of 2026-11-10. The pipeline tour that main has now (#111) has never published one. The pipeline README says the tour's list is replaced whole by each tour, made only by tour --publish. This is that: the whole tour on current main, published by the tour itself. The list then matches the build it ships with.

What changed

The tour's list and its note, replaced by python -I scripts/pipeline_tour.py tour --game <game folder> --out <tour dir> --name play --publish. No other file changes.

  • pipelines: assets/pipeline_states/tour.bin.xz: 10,993 pipelines (9,637 graphics, 790 mesh, 566 compute) of 5,332 programs, from 45 games over the four parts (opening, child overworld, dungeons, adult overworld), from a new save, in 54 minutes of runs. Against the list it replaces (11,227, of which 0 compute), it adds 4,509 pipelines and lacks 4,743.
  • pipelines: assets/pipeline_states/tour.md: as --publish wrote it, except the GPU line. The tour wrote "NVIDIA GeForce RTX 4070 (Vulkan, native)", because it takes the line from the bridge's renderer, which names no driver. I ran the same nx2/pipeline_states.py tour command publish() builds (the 45 runs' lists in its order, the same build, settings and route) with "NVIDIA GeForce RTX 4070, driver 615.71.09 (Linux)", which the runs' logs show (vk: driver: NVIDIA 615.71.09). The list it wrote is byte-identical to the published one.
  • The merged shipped list (nx2/pipeline_states.py merge) goes from 63,920 to 63,717 pipelines: 2,222 that no source had before, and 2,425 that only the old tour's list held. In this build of main the game finds more of the list, not fewer: 32,905 noted pipelines of 20,495 programs at the start, against 32,390 of 20,411, and 2,211 compute programs against 2,199 (Measurements). Most of what drops out is pipelines this build no longer asks for, as the README warns of lists from older builds.

The tour was run on an ext4 drive, so with #898's change to its game copy applied locally. That change touches only how the game folder is copied, not the runs or the lists.

Measurements

Verdict: the build prepares 515 more pipelines (+1.6%) and keeps 12 more compute programs ready. The cost is memory: about 100 to 150 MB more in play, in runs that don't overlap. Start-up times are within the spread between runs.

Before: main @ a8a30c22
After: this PR @ 37b3bc85
Both columns run the same game build: main at a8a30c22 (this PR's base), built from source with nx2/make_game.py and tools.lock's Linux tools. The only difference is longshot_pipeline_states_shipped.bin, merged on main and on this branch. This PR changes only that file's sources, so swapping it is the comparison.
Hardware: Linux (Ubuntu 26.04.1, kernel 7.0), RTX 4070 12 GB, driver 615.71.09, Ryzen 7 5800X3D, 64 GB, NVMe
Scene: a save in Zora's Domain (child), headless, the build's own default options (the Auto preset on this PC: 2560x1440 output, the game's upscaler, no DLSS (a build without it), frame generation off, HDR off, no frame rate cap); RX_VK_LOAD=create
Method: a warm-up round of each, then two rounds interleaved (main, PR, main, PR). Each round: no notes, no Vulkan pipeline cache and no longshot_prepared.bin (cache/longshot_pipelines.bin*, cache/longshot_vk_pipelines*), then the build's step (longshot --prepare-shaders --compile-shaders most), then a first start and a later start. Each start loads the save into play through the control bridge (A once every ~1.5 s from the title until the state is play and not loading) and is measured 30 s into play. Times are by wall clock, so launch to play includes up to ~1.5 s of the presses' spacing. The precompile and load lines are from the game's log. Memory is the process's private bytes (smaps_rollup Private_Clean + Private_Dirty) and its resident set (VmRSS), 30 s into play. The driver's shader cache was shared and warm in both arms (the warm-up rounds filled it).
How to reproduce: python -I nx2/pipeline_states.py merge --out <file> on main and on this branch, each copied over a game folder's longshot_pipeline_states_shipped.bin, with cache/longshot_pipelines.bin*, cache/longshot_vk_pipelines* and cache/longshot_prepared.bin removed first.

Before: main @ a8a30c22 After: this PR @ 37b3bc85 Δ
Pipelines in the merged shipped list 63,920 63,717 −203
Noted pipelines found at a later start (of programs) 32,390 (20,411) 32,905 (20,495) +515
Compute programs kept ready 2,199 2,211 +12
Build's step: noted pipelines built (run 1 / run 2) 33,185 / 33,450 33,707 / 33,965 +520
Build's step, wall (run 1 / run 2, median) 35.8 / 36.2 s, 36.0 s 37.6 / 36.2 s, 36.9 s within spread
Its precompile line 12.1 / 12.1 s 13.2 / 12.1 s within spread
First start: precompile 5.2 / 5.2 s 5.2 / 5.2 s none
First start: launch to play 47.1 / 49.6 s, 48.4 s 49.4 / 49.1 s, 49.3 s within spread
First start: private memory in play 8,574 / 8,620 MB, 8,597 8,743 / 8,735 MB, 8,739 +142 MB
First start: resident set in play 9,106 / 9,172 MB, 9,139 9,299 / 9,283 MB, 9,291 +152 MB
Later start: load at create 823 / 851 ms, 837 857 / 858 ms, 858 +21 ms
Later start: launch to play 44.4 / 44.8 s, 44.6 s 44.5 / 42.7 s, 43.6 s within spread
Later start: private memory in play 8,528 / 8,610 MB, 8,569 8,644 / 8,700 MB, 8,672 +103 MB
Later start: resident set in play 9,059 / 9,157 MB, 9,108 9,192 / 9,264 MB, 9,228 +120 MB

The same measurement on a build of f637b42d (before the rebase onto a8a30c22, whose translator stamp differs) gave the same counts (+515 noted pipelines, +12 compute programs) and memory in the same direction.

main-1 build: vk: precompile: 33185 noted pipelines of 20411 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s
pr-1 build:   vk: precompile: 33707 noted pipelines of 20495 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 13.2 s
main-2 build: vk: precompile: 33450 noted pipelines of 20411 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s
pr-2 build:   vk: precompile: 33965 noted pipelines of 20495 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s
main later:   vk: precompile: load at create (RX_VK_LOAD=create): 32390 noted pipelines found, none built; 2199 compute programs named (2199 in the shipped list, 116 dispatched in play here); ... in 823 ms
pr later:     vk: precompile: load at create (RX_VK_LOAD=create): 32905 noted pipelines found, none built; 2211 compute programs named (2211 in the shipped list, 116 dispatched in play here); ... in 857 ms

Flags and settings

None.

Testing

Tested: Linux (Ubuntu 26.04.1), RTX 4070, driver 615.71.09.

  • python -I nx2/pipeline_states.py check: passes (merged: 63,717 pipelines, 2,211 compute programs, under COMPUTE_MOST).
  • python -I -B tests/run_all.py at 37b3bc85: 545 passed, 20 failed, 80 skipped. The same 20 fail on main a8a30c22 here:
    • test_appimage_player_build, test_bake_portability (no zstandard here), test_bug_report, test_crash_dialog (clang 21 rejects -x none) and test_crt_options
    • test_env_on, test_hardware_report, test_lift_cleanup_error, test_linux_preflight and test_linux_update
    • test_make_game_cache, test_missing_nup, test_mods_size_table, test_options_budget_once and test_pipeline_tour (the stale snapshot that #898 fixes)
    • test_readback_late, test_run_all_changed, test_vk_occlusion_queries, test_vk_pgo and test_walk_key
  • The tour itself: exit 0, 45 games, of which 37 ended at the tour's memory guard (over 9,000 MB after a stop, peaks 9.0 to 10.4 GB) and went on in a fresh game from the next stop. No GPU faults, and the tour's copy was removed with no file in the game folder changed.
  • In the game, the four measured rounds above on a8a30c22, and the same on f637b42d: every start reached play in Zora's Domain at 59 to 60 fps and quit with exit 0.

Not tested:

  • Other GPUs and settings. The list is version 2 (HKSTATE2), which the README says prepares the pipelines of other GPUs, upscalers and output sizes too. Here, only an RTX 4070 at the measured settings.
  • Windows. The same list ships there, but it wasn't measured there.

Must be tested: None.

Risks

What could break: the 2,425 pipelines that only the old tour's list held are no longer prepared before the title. In this build most of them aren't asked for (the noted count rises by 515), but a few may be, and would then compile the first time the game meets them, as before that list. The game holds about 100 to 150 MB more in play here (Measurements).

Turning it off: revert the commit.

Compatibility: a build from this PR prepares the new merged list at its first start, as any list change does. Saves, settings and the caches' formats don't change.

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. Not ticked yet: Memory cost is measured only on one RTX 4070 under Linux, and Testing says other GPUs, settings and Windows were not measured.
  • 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.
  • Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported.

🤖 Generated with Claude Code

**Type:** build · **Risk:** low · **Tested on:** Linux (Ubuntu 26.04.1), RTX 4070 · **Needs:** none ## Why `assets/pipeline_states/tour.bin.xz` is still the list from the draft tour (Hookshot's PR 2048) on main of 2026-11-10. The pipeline tour that main has now (#111) has never published one. The pipeline README says the tour's list is replaced whole by each tour, made only by `tour --publish`. This is that: the whole tour on current main, published by the tour itself. The list then matches the build it ships with. ## What changed The tour's list and its note, replaced by `python -I scripts/pipeline_tour.py tour --game <game folder> --out <tour dir> --name play --publish`. No other file changes. - pipelines: `assets/pipeline_states/tour.bin.xz`: 10,993 pipelines (9,637 graphics, 790 mesh, 566 compute) of 5,332 programs, from 45 games over the four parts (opening, child overworld, dungeons, adult overworld), from a new save, in 54 minutes of runs. Against the list it replaces (11,227, of which 0 compute), it adds 4,509 pipelines and lacks 4,743. - pipelines: `assets/pipeline_states/tour.md`: as `--publish` wrote it, except the GPU line. The tour wrote "NVIDIA GeForce RTX 4070 (Vulkan, native)", because it takes the line from the bridge's renderer, which names no driver. I ran the same `nx2/pipeline_states.py tour` command `publish()` builds (the 45 runs' lists in its order, the same build, settings and route) with "NVIDIA GeForce RTX 4070, driver 615.71.09 (Linux)", which the runs' logs show (`vk: driver: NVIDIA 615.71.09`). The list it wrote is byte-identical to the published one. - **The merged shipped list** (`nx2/pipeline_states.py merge`) goes from 63,920 to 63,717 pipelines: 2,222 that no source had before, and 2,425 that only the old tour's list held. In this build of main the game finds more of the list, not fewer: 32,905 noted pipelines of 20,495 programs at the start, against 32,390 of 20,411, and 2,211 compute programs against 2,199 (Measurements). Most of what drops out is pipelines this build no longer asks for, as the README warns of lists from older builds. The tour was run on an ext4 drive, so with #898's change to its game copy applied locally. That change touches only how the game folder is copied, not the runs or the lists. ## Measurements **Verdict:** the build prepares 515 more pipelines (+1.6%) and keeps 12 more compute programs ready. The cost is memory: about 100 to 150 MB more in play, in runs that don't overlap. Start-up times are within the spread between runs. Before: main @ a8a30c22 After: this PR @ 37b3bc85 Both columns run the same game build: main at a8a30c22 (this PR's base), built from source with `nx2/make_game.py` and tools.lock's Linux tools. The only difference is `longshot_pipeline_states_shipped.bin`, merged on main and on this branch. This PR changes only that file's sources, so swapping it is the comparison. Hardware: Linux (Ubuntu 26.04.1, kernel 7.0), RTX 4070 12 GB, driver 615.71.09, Ryzen 7 5800X3D, 64 GB, NVMe Scene: a save in Zora's Domain (child), headless, the build's own default options (the Auto preset on this PC: 2560x1440 output, the game's upscaler, no DLSS (a build without it), frame generation off, HDR off, no frame rate cap); `RX_VK_LOAD=create` Method: a warm-up round of each, then two rounds interleaved (main, PR, main, PR). Each round: no notes, no Vulkan pipeline cache and no `longshot_prepared.bin` (`cache/longshot_pipelines.bin*`, `cache/longshot_vk_pipelines*`), then the build's step (`longshot --prepare-shaders --compile-shaders most`), then a first start and a later start. Each start loads the save into play through the control bridge (A once every ~1.5 s from the title until the state is play and not loading) and is measured 30 s into play. Times are by wall clock, so launch to play includes up to ~1.5 s of the presses' spacing. The precompile and load lines are from the game's log. Memory is the process's private bytes (smaps_rollup Private_Clean + Private_Dirty) and its resident set (VmRSS), 30 s into play. The driver's shader cache was shared and warm in both arms (the warm-up rounds filled it). How to reproduce: `python -I nx2/pipeline_states.py merge --out <file>` on main and on this branch, each copied over a game folder's `longshot_pipeline_states_shipped.bin`, with `cache/longshot_pipelines.bin*`, `cache/longshot_vk_pipelines*` and `cache/longshot_prepared.bin` removed first. | | Before: main @ a8a30c22 | After: this PR @ 37b3bc85 | Δ | |---|---|---|---| | Pipelines in the merged shipped list | 63,920 | 63,717 | −203 | | Noted pipelines found at a later start (of programs) | 32,390 (20,411) | 32,905 (20,495) | +515 | | Compute programs kept ready | 2,199 | 2,211 | +12 | | Build's step: noted pipelines built (run 1 / run 2) | 33,185 / 33,450 | 33,707 / 33,965 | +520 | | Build's step, wall (run 1 / run 2, median) | 35.8 / 36.2 s, 36.0 s | 37.6 / 36.2 s, 36.9 s | within spread | | Its precompile line | 12.1 / 12.1 s | 13.2 / 12.1 s | within spread | | First start: precompile | 5.2 / 5.2 s | 5.2 / 5.2 s | none | | First start: launch to play | 47.1 / 49.6 s, 48.4 s | 49.4 / 49.1 s, 49.3 s | within spread | | First start: private memory in play | 8,574 / 8,620 MB, 8,597 | 8,743 / 8,735 MB, 8,739 | +142 MB | | First start: resident set in play | 9,106 / 9,172 MB, 9,139 | 9,299 / 9,283 MB, 9,291 | +152 MB | | Later start: load at create | 823 / 851 ms, 837 | 857 / 858 ms, 858 | +21 ms | | Later start: launch to play | 44.4 / 44.8 s, 44.6 s | 44.5 / 42.7 s, 43.6 s | within spread | | Later start: private memory in play | 8,528 / 8,610 MB, 8,569 | 8,644 / 8,700 MB, 8,672 | +103 MB | | Later start: resident set in play | 9,059 / 9,157 MB, 9,108 | 9,192 / 9,264 MB, 9,228 | +120 MB | The same measurement on a build of f637b42d (before the rebase onto a8a30c22, whose translator stamp differs) gave the same counts (+515 noted pipelines, +12 compute programs) and memory in the same direction. ``` main-1 build: vk: precompile: 33185 noted pipelines of 20411 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s pr-1 build: vk: precompile: 33707 noted pipelines of 20495 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 13.2 s main-2 build: vk: precompile: 33450 noted pipelines of 20411 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s pr-2 build: vk: precompile: 33965 noted pipelines of 20495 programs and 9927 compute pipelines of 4128 compute programs built into the pipeline cache and let go (0 and 0 not made, 0 whose program variant is not kept), on 16 threads in 12.1 s main later: vk: precompile: load at create (RX_VK_LOAD=create): 32390 noted pipelines found, none built; 2199 compute programs named (2199 in the shipped list, 116 dispatched in play here); ... in 823 ms pr later: vk: precompile: load at create (RX_VK_LOAD=create): 32905 noted pipelines found, none built; 2211 compute programs named (2211 in the shipped list, 116 dispatched in play here); ... in 857 ms ``` ### Flags and settings None. ## Testing **Tested:** Linux (Ubuntu 26.04.1), RTX 4070, driver 615.71.09. - `python -I nx2/pipeline_states.py check`: passes (merged: 63,717 pipelines, 2,211 compute programs, under `COMPUTE_MOST`). - `python -I -B tests/run_all.py` at 37b3bc85: 545 passed, 20 failed, 80 skipped. The same 20 fail on main a8a30c22 here: - `test_appimage_player_build`, `test_bake_portability` (no `zstandard` here), `test_bug_report`, `test_crash_dialog` (clang 21 rejects `-x none`) and `test_crt_options` - `test_env_on`, `test_hardware_report`, `test_lift_cleanup_error`, `test_linux_preflight` and `test_linux_update` - `test_make_game_cache`, `test_missing_nup`, `test_mods_size_table`, `test_options_budget_once` and `test_pipeline_tour` (the stale snapshot that #898 fixes) - `test_readback_late`, `test_run_all_changed`, `test_vk_occlusion_queries`, `test_vk_pgo` and `test_walk_key` - The tour itself: exit 0, 45 games, of which 37 ended at the tour's memory guard (over 9,000 MB after a stop, peaks 9.0 to 10.4 GB) and went on in a fresh game from the next stop. No GPU faults, and the tour's copy was removed with no file in the game folder changed. - In the game, the four measured rounds above on a8a30c22, and the same on f637b42d: every start reached play in Zora's Domain at 59 to 60 fps and quit with exit 0. **Not tested:** - **Other GPUs and settings.** The list is version 2 (`HKSTATE2`), which the README says prepares the pipelines of other GPUs, upscalers and output sizes too. Here, only an RTX 4070 at the measured settings. - **Windows.** The same list ships there, but it wasn't measured there. **Must be tested:** None. ## Risks **What could break:** the 2,425 pipelines that only the old tour's list held are no longer prepared before the title. In this build most of them aren't asked for (the noted count rises by 515), but a few may be, and would then compile the first time the game meets them, as before that list. The game holds about 100 to 150 MB more in play here (Measurements). **Turning it off:** revert the commit. **Compatibility:** a build from this PR prepares the new merged list at its first start, as any list change does. Saves, settings and the caches' formats don't change. ## 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. - [ ] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. Not ticked yet: Memory cost is measured only on one RTX 4070 under Linux, and Testing says other GPUs, settings and Windows were not measured. - [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] Numbers from the same PC, scene and settings, at least 2 interleaved runs each, the median reported. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
build(release): the pipeline tour's list from a tour of main f637b42d, 10993 pipelines
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 3s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
37b3bc858d
The whole tour (opening, child overworld, dungeons, adult overworld, from a new save) on main f637b42d,
built from source, on Linux with an RTX 4070 (driver 615.71.09), published by tour --publish. The note's
GPU line names the driver, which the tour's note left out (the game's renderer line has none).

Assisted-by: Claude Opus 5.5
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Rsud93pkyqbpFmD6UmG1Bu
Author
First-time contributor

Measured again on a build of this PR's base, main a8a30c22, after the rebase (its translator stamp differs from f637b42d's). The pipeline counts are the same (+515 noted pipelines, +12 compute programs). The first start's precompile is now 5.2 s on both sides, so the +0.9 s seen on f637b42d did not repeat. Memory in play is about 100 to 150 MB higher with this list, in runs that don't overlap; the description's Measurements and Risks now say so.

Measured again on a build of this PR's base, main a8a30c22, after the rebase (its translator stamp differs from f637b42d's). The pipeline counts are the same (+515 noted pipelines, +12 compute programs). The first start's precompile is now 5.2 s on both sides, so the +0.9 s seen on f637b42d did not repeat. Memory in play is about 100 to 150 MB higher with this list, in runs that don't overlap; the description's Measurements and Risks now say so.
jabbaxipil changed title from WIP: build(release): the pipeline tour's list from a tour of main f637b42d, 10993 pipelines to build(release): the pipeline tour's list from a tour of main f637b42d, 10993 pipelines 2026-11-15 23:31:08 +00:00
jabbaxipil force-pushed tour-list from 37b3bc858d
Some checks failed
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 3s
CI / Conventional Commit title (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been cancelled
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been cancelled
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been cancelled
CI / Workflow lint (actionlint) (pull_request) Has been cancelled
Guide screenshots / Guide images and local UI source review (pull_request) Has been cancelled
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
to 249c371fe2
Some checks failed
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Failing after 10s
2026-11-16 20:00:16 +00:00
Compare
Owner

Brought up to the ready-for-review standard (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know).

  • Tested on my own PC: ticked: Testing's Tested: in-game rounds and the tour run on the author's Ubuntu 26.04 PC with an RTX 4070.
  • Nothing gets worse that I know of: not ticked: Memory cost is measured only on one RTX 4070 under Linux, and Testing says other GPUs, settings and Windows were not measured. Measure that cost and state it in Risks, then tick it.
Brought up to the [ready-for-review standard](https://git.magicbean.dev/MagicBeanDev/Longshot/src/branch/main/CONTRIBUTING.md#ready-for-review-out-of-wip) (#1454): the checklist's Everyone list has two new boxes, added here from what this PR's description and comments show (please check they match what you know). - *Tested on my own PC*: ticked: Testing's Tested: in-game rounds and the tour run on the author's Ubuntu 26.04 PC with an RTX 4070. - *Nothing gets worse that I know of*: not ticked: Memory cost is measured only on one RTX 4070 under Linux, and Testing says other GPUs, settings and Windows were not measured. Measure that cost and state it in Risks, then tick it.
Some checks failed
CI / Conventional Commit title (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Blocked by required conditions
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Blocked by required conditions
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Blocked by required conditions
CI / Workflow lint (actionlint) (pull_request) Blocked by required conditions
Guide screenshots / Guide images and local UI source review (pull_request) Blocked by required conditions
Third-party parts / As their notes say (pull_request) Blocked by required conditions
Third-party parts / The same as upstream (pull_request) Blocked by required conditions
Website / Website on Cloudflare (pull_request) Blocked by required conditions
PR description / Description follows the template (pull_request_target) Failing after 10s
This pull request doesn't have enough approvals yet. 0 of 1 approvals granted.
Some workflows are waiting to be reviewed.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'tour-list:jabbaxipil-tour-list'
git switch 'jabbaxipil-tour-list'
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!957
No description provided.