fix(menu): the Save my pipeline list module includes the POSIX headers it uses #1807

Merged
HumanBean merged 1 commit from mooki/Longshot:fix-pipeline-list-posix into main 2026-11-20 00:30:02 +00:00
Member

Type: fix · Risk: low · Tested on: Linux, RTX 4090 · Needs: Windows, any GPU

TL;DR

Since the menu rows moved into modules (#1774), main does not build on Linux: one of the new files, the Save my pipeline list module, lost the block of system headers its Linux code needs. This puts that block back, ten lines in one file. With it the whole game builds again (152 files compiled, none failed) and starts to the playable game on an RTX 4090.

Breakdown

  • Who it helps: anyone who builds the game on Linux, and every open menu pull request that has to be built there to be tested.
  • What was wrong: gpu/vk/menu/pipeline_list.cpp took the zip-and-open code out of vk_menu.cpp but not the #include block that code needs on Linux.
  • What changes: the module includes those headers again, in the #else of the _WIN32 include it already has.
  • What does not change: the Windows build (the new lines are not seen there), the menu, its rows, the zip, and every other file.
  • How it was checked: the same tree built with and without this change on Linux, one start of the built game, and the Windows-target syntax of the file.
  • What is still open: nothing found; a Windows build of this head was not run.
  • Risk: low: only headers, in a file whose Linux half did not compile.

Why

Main stopped building on Linux with #1774: the build compiles every file of gpu/vk/menu/, and this one uses posix_spawn, waitpid, sigtimedwait, SIGPIPE and uname without including what declares them. Nothing on Linux, including the Test Farm's Linux machines and anyone's own build, can get past it.

How to reproduce

Seen on: Arch Linux, clang, a standalone build with the project's builder over a finished work folder
Settings and switches: defaults
Steps: build main at 0de25c3e4a for Linux
Expected: the build finishes
Actual: it stops in gpu/vk/menu/pipeline_list.cpp ("compiled in 55s, 1 failed"):

pipeline_list.cpp:135:24: error: use of undeclared identifier 'u'
pipeline_list.cpp:189:5: error: unknown type name 'posix_spawn_file_actions_t'
pipeline_list.cpp:192:24: error: use of undeclared identifier 'O_CLOEXEC'
pipeline_list.cpp:215:13: error: use of undeclared identifier 'waitpid'
pipeline_list.cpp:225:26: error: use of undeclared identifier 'SIGPIPE'
pipeline_list.cpp:226:21: error: use of undeclared identifier 'SIG_BLOCK'
pipeline_list.cpp:239:12: error: use of undeclared identifier 'sigtimedwait'
pipeline_list.cpp:242:12: error: use of undeclared identifier 'waitpid'
fatal error: too many errors emitted, stopping now [-ferror-limit=]

What changed

The module's include block gets, for everything but Windows, the headers vk_menu.cpp had for this code before #1774: fcntl.h, spawn.h, csignal, cerrno, pthread.h, sys/utsname.h, sys/wait.h, unistd.h and extern char** environ.

  • gpu/vk/menu/pipeline_list.cpp: the #else branch of the #ifdef _WIN32 include, inside #ifndef MENU_LAYOUT_ONLY, as the code that uses it is.

Measurements

Verdict: nothing to measure for speed: ten lines of headers, no code and no data change.

Hardware: Linux 7.2, RTX 4090 (NVIDIA driver), Core i9-13900K
Scene: the game started windowless from a disposable save, in the Kokiri Forest
Method: the project's builder over a finished work folder of main (whose lift inputs equal this head's), once on main and once on this head; one game start in the side lane
How to reproduce: python -I nx2/make_game.py --romfs ... --exefs ... --out <copy> --work <work folder> on both heads

Before: main @ 0de25c3e4a After: this PR @ 8a1fc7d5c1
Linux build compiled in 55s, 1 failed (pipeline_list.cpp) exit 0, compiled in 44s, 0 failed, 152 new and 405 cached files

Flags and settings

None.

Testing

Tested: on Linux (RTX 4090), this head built with the builder (v3.0.0-rc.8-70-g8a1fc7d5c1 (source 14be9eeb)) and started once windowless: longshot v3.0.0-rc.8-70-g8a1fc7d5c1 (source 14be9eeb), Link controllable after 37.6 s, fatal=0 crash=0 devlost=0 nocore=0 kernel=0 nvrm=0. The whole suite was not run (ten lines of headers); the 108 game-free checks that read the menu's sources ran through the idle gate on main and on this head: 98 pass and the same 10 fail on both (test_bug_report_defaults, test_crash_dialog, test_crt_options, test_damage_debug_menu, test_dev_packs, test_hud_layout_row, test_mods_size_table, test_present_queue_default, test_upscaler_rows, test_walk_key). The Windows-target syntax of the file (x86_64-w64-mingw32-clang++ -std=c++20 -fsyntax-only -Wall -Wextra) passes on both heads.

Not tested: a Windows build and run (the lines are in the branch Windows does not compile); the zip, clipboard and browser steps of Save my pipeline list in the game (the code is unchanged).

Must be tested:

  • Windows, any GPU: build this head, expecting it to build as main does (Test Farm: @Beanstalk windows, build and start this head)

Risks

What could break: a Linux build that already worked cannot be made worse by headers; a name from these headers colliding with the file's own would stop the build, and the build above says it does not.

Turning it off: revert the commit.

Compatibility: Nothing changes.

Issues

See #1774

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.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.

New on this forge; not opened on GitHub.

**Type:** fix · **Risk:** low · **Tested on:** Linux, RTX 4090 · **Needs:** Windows, any GPU ## TL;DR Since the menu rows moved into modules (#1774), main does not build on Linux: one of the new files, the Save my pipeline list module, lost the block of system headers its Linux code needs. This puts that block back, ten lines in one file. With it the whole game builds again (152 files compiled, none failed) and starts to the playable game on an RTX 4090. ## Breakdown - **Who it helps:** anyone who builds the game on Linux, and every open menu pull request that has to be built there to be tested. - **What was wrong:** `gpu/vk/menu/pipeline_list.cpp` took the zip-and-open code out of `vk_menu.cpp` but not the `#include` block that code needs on Linux. - **What changes:** the module includes those headers again, in the `#else` of the `_WIN32` include it already has. - **What does not change:** the Windows build (the new lines are not seen there), the menu, its rows, the zip, and every other file. - **How it was checked:** the same tree built with and without this change on Linux, one start of the built game, and the Windows-target syntax of the file. - **What is still open:** nothing found; a Windows build of this head was not run. - **Risk:** low: only headers, in a file whose Linux half did not compile. ## Why Main stopped building on Linux with #1774: the build compiles every file of `gpu/vk/menu/`, and this one uses `posix_spawn`, `waitpid`, `sigtimedwait`, `SIGPIPE` and `uname` without including what declares them. Nothing on Linux, including the Test Farm's Linux machines and anyone's own build, can get past it. ## How to reproduce **Seen on:** Arch Linux, clang, a standalone build with the project's builder over a finished work folder **Settings and switches:** defaults **Steps:** build main at `0de25c3e4a` for Linux **Expected:** the build finishes **Actual:** it stops in `gpu/vk/menu/pipeline_list.cpp` ("compiled in 55s, 1 failed"): ``` pipeline_list.cpp:135:24: error: use of undeclared identifier 'u' pipeline_list.cpp:189:5: error: unknown type name 'posix_spawn_file_actions_t' pipeline_list.cpp:192:24: error: use of undeclared identifier 'O_CLOEXEC' pipeline_list.cpp:215:13: error: use of undeclared identifier 'waitpid' pipeline_list.cpp:225:26: error: use of undeclared identifier 'SIGPIPE' pipeline_list.cpp:226:21: error: use of undeclared identifier 'SIG_BLOCK' pipeline_list.cpp:239:12: error: use of undeclared identifier 'sigtimedwait' pipeline_list.cpp:242:12: error: use of undeclared identifier 'waitpid' fatal error: too many errors emitted, stopping now [-ferror-limit=] ``` ## What changed The module's include block gets, for everything but Windows, the headers `vk_menu.cpp` had for this code before #1774: `fcntl.h`, `spawn.h`, `csignal`, `cerrno`, `pthread.h`, `sys/utsname.h`, `sys/wait.h`, `unistd.h` and `extern char** environ`. - `gpu/vk/menu/pipeline_list.cpp`: the `#else` branch of the `#ifdef _WIN32` include, inside `#ifndef MENU_LAYOUT_ONLY`, as the code that uses it is. ## Measurements **Verdict:** nothing to measure for speed: ten lines of headers, no code and no data change. Hardware: Linux 7.2, RTX 4090 (NVIDIA driver), Core i9-13900K Scene: the game started windowless from a disposable save, in the Kokiri Forest Method: the project's builder over a finished work folder of main (whose lift inputs equal this head's), once on main and once on this head; one game start in the side lane How to reproduce: `python -I nx2/make_game.py --romfs ... --exefs ... --out <copy> --work <work folder>` on both heads | | Before: main @ 0de25c3e4a | After: this PR @ 8a1fc7d5c1 | |---|---|---| | Linux build | compiled in 55s, 1 failed (`pipeline_list.cpp`) | exit 0, compiled in 44s, 0 failed, 152 new and 405 cached files | ### Flags and settings None. ## Testing **Tested:** on Linux (RTX 4090), this head built with the builder (`v3.0.0-rc.8-70-g8a1fc7d5c1 (source 14be9eeb)`) and started once windowless: `longshot v3.0.0-rc.8-70-g8a1fc7d5c1 (source 14be9eeb)`, Link controllable after 37.6 s, fatal=0 crash=0 devlost=0 nocore=0 kernel=0 nvrm=0. The whole suite was not run (ten lines of headers); the 108 game-free checks that read the menu's sources ran through the idle gate on main and on this head: 98 pass and the same 10 fail on both (`test_bug_report_defaults`, `test_crash_dialog`, `test_crt_options`, `test_damage_debug_menu`, `test_dev_packs`, `test_hud_layout_row`, `test_mods_size_table`, `test_present_queue_default`, `test_upscaler_rows`, `test_walk_key`). The Windows-target syntax of the file (`x86_64-w64-mingw32-clang++ -std=c++20 -fsyntax-only -Wall -Wextra`) passes on both heads. **Not tested:** a Windows build and run (the lines are in the branch Windows does not compile); the zip, clipboard and browser steps of Save my pipeline list in the game (the code is unchanged). **Must be tested:** - Windows, any GPU: build this head, expecting it to build as main does (Test Farm: @Beanstalk windows, build and start this head) ## Risks **What could break:** a Linux build that already worked cannot be made worse by headers; a name from these headers colliding with the file's own would stop the build, and the build above says it does not. **Turning it off:** revert the commit. **Compatibility:** Nothing changes. ## Issues See #1774 ## 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] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. --- New on this forge; not opened on GitHub.
fix(menu): the Save my pipeline list module includes the POSIX headers it uses
Some checks reported errors
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_target) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 26s
PR description / Description follows the template (pull_request_target) Successful in 32s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 38s
CI / Workflow lint (actionlint) (pull_request) Successful in 39s
Third-party parts / As their notes say (pull_request) Successful in 43s
beanstalk/approval approved by mooki (reviewed)
beanstalk/linux 0/1 pass, 2 error
beanstalk/windows 2/1 pass
8a1fc7d5c1
gpu/vk/menu/pipeline_list.cpp took the Save my pipeline list code out of vk_menu.cpp (#1633) without the block of POSIX
headers vk_menu.cpp had for it (fcntl.h, spawn.h, csignal, cerrno, pthread.h, sys/utsname.h, sys/wait.h, unistd.h, and
environ), so a Linux build stopped in that one file: posix_spawn_file_actions_t, waitpid, SIGPIPE, sigtimedwait and
utsname were undeclared. The block is here again, in the module, under the same Windows/other split the code has.

Assisted-by: Claude Sonnet 5.5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Author
Member

Main has not built on Linux since the menu model (#1774): gpu/vk/menu/pipeline_list.cpp lost the block of POSIX headers that vk_menu.cpp had for Save my pipeline list, so the one file fails with posix_spawn_file_actions_t, waitpid, SIGPIPE, sigtimedwait and utsname undeclared.
This PR puts that block back in the module, under the _WIN32 split the code already has; nothing else changes (10 lines, one file).
On Linux (RTX 4090) the build of this head is clean (152 files compiled, 0 failed) and it started once, windowless, to the playable game with no fatal, crash or device-loss line; main alone stops at that file. The Windows branch is unchanged and the file still passes a Windows-target syntax check.
Every open menu PR that is built on Linux needs this first.

Main has not built on Linux since the menu model (#1774): `gpu/vk/menu/pipeline_list.cpp` lost the block of POSIX headers that `vk_menu.cpp` had for Save my pipeline list, so the one file fails with `posix_spawn_file_actions_t`, `waitpid`, `SIGPIPE`, `sigtimedwait` and `utsname` undeclared. This PR puts that block back in the module, under the `_WIN32` split the code already has; nothing else changes (10 lines, one file). On Linux (RTX 4090) the build of this head is clean (152 files compiled, 0 failed) and it started once, windowless, to the playable game with no fatal, crash or device-loss line; main alone stops at that file. The Windows branch is unchanged and the file still passes a Windows-target syntax check. Every open menu PR that is built on Linux needs this first.
mooki changed title from WIP: fix(menu): the Save my pipeline list module includes the POSIX headers it uses to fix(menu): the Save my pipeline list module includes the POSIX headers it uses 2026-11-19 22:40:28 +00:00
Author
Member

@Beanstalk

@Beanstalk
Member

Beanstalk test farm

Commit 8a1fc7d · tier reviewed · approved by mooki · dashboard

What will be tested · AI plan (gpt-6.1-terra)

The farm builds main and the PR on Linux and Windows, then loads the Kokiri Forest checkpoint and waits for play. The smoke test takes about 10 minutes per target, excluding builds; a failed PR build or start fails the test. Main is reported not to build on Linux, which may block the Linux comparison rather than indicate a PR regression.

  • Where: linux (1-2 reports), windows (1-2 reports).
  • kokiri-start: from the repository's save kokiri-start; 1 run on each side.
  • Measured: crashes.
  • The PR fails if: it crashes.
  • Time: about 10 min of game runs per tester (2 game starts), plus the two builds.

Done (started 2026-11-19 22:41 UTC, last report 2026-11-19 23:06 UTC). Comment @Beanstalk to run it again.

Target Reports Crash Frame p99 (ms) vs main VRAM peak (MB) vs main Result
linux · 1: linux+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 5070, 620.70.6; 2: linux+amd+radv+igpu AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8 2/1 1 2 none — — error
windows · 1: windows+amd+amd-proprietary+dgpu AMD Radeon RX 9060 XT, 2.0.416; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0 2/1 1 2 none — — pass

Measurements · linux

Verdict: could not be judged on linux (2/1 report).

Hardware: 1: linux+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 5070, 620.70.6 AMD Ryzen 5 9600X 6-Core Processor, 32 GB RAM; 2: linux+amd+radv+igpu AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8 AMD Ryzen 5 230 w/ Radeon 760M Graphics, 16 GB RAM
Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Nothing was measured: no metric came back.

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** could not be judged on linux (2/1 report).

Hardware: 1: linux+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 5070, 620.70.6` `AMD Ryzen 5 9600X 6-Core Processor, 32 GB RAM`; 2: linux+amd+radv+igpu `AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8` `AMD Ryzen 5 230 w/ Radeon 760M Graphics, 16 GB RAM`  
Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

Nothing was measured: no metric came back.

### Flags and settings

None: the plan varied no setting, switch or build option.

Measurements · windows

Verdict: pass on windows (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+amd+amd-proprietary+dgpu AMD Radeon RX 9060 XT, 2.0.416 AMD Ryzen 5 5600 6-Core Processor, 32 GB RAM; 2: windows+nvidia+nvidia-proprietary+dgpu NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0 AMD Ryzen 7 7800X3D 8-Core Processor, 32 GB RAM
Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports
How to reproduce: the farm's plan above (@Beanstalk on this PR runs it again)

Nothing was measured: no metric came back.

Flags and settings

None: the plan varied no setting, switch or build option.

Markdown for the PR description
## Measurements

**Verdict:** pass on windows (2/1 report): no rule failed and no PR run crashed.

Hardware: 1: windows+amd+amd-proprietary+dgpu `AMD Radeon RX 9060 XT, 2.0.416` `AMD Ryzen 5 5600 6-Core Processor, 32 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0` `AMD Ryzen 7 7800X3D 8-Core Processor, 32 GB RAM`  
Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them  
Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports  
How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again)

Nothing was measured: no metric came back.

### Flags and settings

None: the plan varied no setting, switch or build option.
<!-- beanstalk:sticky --> ### Beanstalk test farm Commit `8a1fc7d` · tier **reviewed** · approved by mooki · [dashboard](https://beanstalk.magicbean.dev/prs/1807) **What will be tested** · AI plan (`gpt-6.1-terra`) The farm builds main and the PR on Linux and Windows, then loads the Kokiri Forest checkpoint and waits for play. The smoke test takes about 10 minutes per target, excluding builds; a failed PR build or start fails the test. Main is reported not to build on Linux, which may block the Linux comparison rather than indicate a PR regression. - **Where:** linux (1-2 reports), windows (1-2 reports). - **kokiri-start:** from the repository's save `kokiri-start`; 1 run on each side. - **Measured:** crashes. - **The PR fails if:** it crashes. - **Time:** about 10 min of game runs per tester (2 game starts), plus the two builds. Done (started 2026-11-19 22:41 UTC, last report 2026-11-19 23:06 UTC). Comment `@Beanstalk` to run it again. | Target | Reports | Crash | Frame p99 (ms) vs main | VRAM peak (MB) vs main | Result | | --- | --- | --- | --- | --- | --- | | linux · 1: linux+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 5070, 620.70.6`; 2: linux+amd+radv+igpu `AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_eb8ec8ddb73b025e) [2](https://beanstalk.magicbean.dev/reports/rp_9e3f6008cf6fb730) | none | — | — | error | | windows · 1: windows+amd+amd-proprietary+dgpu `AMD Radeon RX 9060 XT, 2.0.416`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0` | 2/1 [1](https://beanstalk.magicbean.dev/reports/rp_9ccbb080a7bbff39) [2](https://beanstalk.magicbean.dev/reports/rp_71fb8f9d9a11dabc) | none | — | — | pass | #### Measurements · linux **Verdict:** could not be judged on linux (2/1 report). Hardware: 1: linux+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 5070, 620.70.6` `AMD Ryzen 5 9600X 6-Core Processor, 32 GB RAM`; 2: linux+amd+radv+igpu `AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8` `AMD Ryzen 5 230 w/ Radeon 760M Graphics, 16 GB RAM` Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** could not be judged on linux (2/1 report). Hardware: 1: linux+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 5070, 620.70.6` `AMD Ryzen 5 9600X 6-Core Processor, 32 GB RAM`; 2: linux+amd+radv+igpu `AMD Radeon 760M Graphics (RADV PHOENIX), 26.0.8` `AMD Ryzen 5 230 w/ Radeon 760M Graphics, 16 GB RAM` Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details> #### Measurements · windows **Verdict:** pass on windows (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+amd+amd-proprietary+dgpu `AMD Radeon RX 9060 XT, 2.0.416` `AMD Ryzen 5 5600 6-Core Processor, 32 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0` `AMD Ryzen 7 7800X3D 8-Core Processor, 32 GB RAM` Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. <details><summary>Markdown for the PR description</summary> ```markdown ## Measurements **Verdict:** pass on windows (2/1 report): no rule failed and no PR run crashed. Hardware: 1: windows+amd+amd-proprietary+dgpu `AMD Radeon RX 9060 XT, 2.0.416` `AMD Ryzen 5 5600 6-Core Processor, 32 GB RAM`; 2: windows+nvidia+nvidia-proprietary+dgpu `NVIDIA GeForce RTX 4070 Ti SUPER, 621.14.0` `AMD Ryzen 7 7800X3D 8-Core Processor, 32 GB RAM` Scene: kokiri-start, from the repository's save kokiri-start; each cell's settings and switches as the table names them Method: the Beanstalk test farm: main and this PR built and run on the same PC in one session, game starts alternating (ABBA); kokiri-start: 1 game start a side; each number the median of the runs, then of 2 reports How to reproduce: the farm's plan above (`@Beanstalk` on this PR runs it again) Nothing was measured: no metric came back. ### Flags and settings None: the plan varied no setting, switch or build option. ``` </details>
HumanBean deleted branch fix-pipeline-list-posix 2026-11-20 00:30:03 +00:00
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!1807
No description provided.