WIP: fix(vk): report the shader preparation countdown to builders #1830

Draft
futondestroyer wants to merge 4 commits from futondestroyer/Longshot:fix/renderer-shader-eta into main
Member

Summary

The Launcher can only infer shader preparation time from an overall fraction. That fraction can jump when the renderer finds reusable work or changes from shader programs to pipelines. The prepare-only renderer now emits its own recent-rate estimate and clears it as the work changes or the pipeline cache is written.

The producer is in vk_progress.h and vk_main.cpp. The existing saving intervals in vk_draw.cpp emit their status only in prepare-only mode. make_game.py forwards the new shader event and keeps the renderer's exit separate from the builder's completion. The Launcher consumer is PR #213.

Testing

Tested: Windows 11 build 26300, NVIDIA RTX 4070 driver 32.0.16.2101. Both earlier exact runtimes completed real --prepare-shaders runs at Most. The patched renderer emitted 432 scoped signals, including two cache-saving events, and exited successfully. The relay regression failed on main because it stripped @@shader_eta unknown and passed on the patch. Five focused Windows checks passed after the first two assertions were updated. The test-only follow-up at 06cb158f fixed the extracted prepare-cache and quit fixtures while preserving the renderer and builder source used by the game-tested runtime at 3d544fc7.

The interrupted Windows runner emitted KeyboardInterrupt and exited with Windows STATUS_CONTROL_C_EXIT (0xC000013A). Separate process groups completed all eight supported tests/run_all.py --strict --shard K/8 shards. The exact base 068fb8eb had 751 passes, 71 failures and 48 skips. The producer comparison had 752 passes, 70 failures and 48 skips across the same 870 checks. It reran the three shards containing the four changed fixture files and reused the results for the other, unchanged checks. The final revision also passed the tracked Python byte-compile check.

tests/test_prepare_cache_save.py is the sole outcome that changed. The repaired fixture exercises the actual saving helper, checks its flag during the forced write, and verifies the saving and unknown events. Its Most refresh expectation now matches the renderer's existing progress calculation. A second matched run with the full repository-pinned Python packages, the supported llvm-mingw configuration and .NET 8 cleared test_fpx_sticky.py, test_make_game_cache.py, test_portable_builder_home.py and test_walk.py on both sides.

Rebase validation: Replayed the published stack onto 89c3d21e. Git's independent merge calculation matches a74e3677 exactly. The relay regression failed at the test-only commit with the expected dropped @@shader_eta unknown signal. The rebased head passed all eight focused Windows checks and built the full Windows renderer with dev.py vk, including its export check. The latest main failed only the known Most-refresh expectation among the seven comparable focused tests. The 870-check comparison above applies to the earlier main and producer pair.

The Guide screenshots / Guide images and local UI source review check reports the same 33 source-review items on current main and the rebased head. The Guide source review and its recorded hashes need attention on main for green merge CI. The two CI / Python source checks (ubuntu-24.04, part 1/2) and CI / Python source checks (ubuntu-24.04, part 2/2) jobs and CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) are manual dispatch jobs. A Linux runner is still needed for the applicable host build and UTF-8 path checklist item.

70 named failures reproduced on the earlier main, 068fb8eb
  • tests/test_appimage_player_build.py
  • tests/test_auto_handheld.py
  • tests/test_bug_report_defaults.py
  • tests/test_build_long_paths.py
  • tests/test_capture_read_once.py
  • tests/test_capture_readback_visibility.py
  • tests/test_crash_dialog.py
  • tests/test_crt_options.py
  • tests/test_damage_debug_menu.py
  • tests/test_dev_ab.py
  • tests/test_dev_build.py
  • tests/test_dev_migrate.py
  • tests/test_dev_packs.py
  • tests/test_discover.py
  • tests/test_display_startup_failure.py
  • tests/test_dlss_feature_size.py
  • tests/test_draw_stream_visibility.py
  • tests/test_failed_compile_keeps_objects.py
  • tests/test_fastfp_fma.py
  • tests/test_fma_soft.py
  • tests/test_fpx_sticky.py
  • tests/test_frame_overlap.py
  • tests/test_fsr3fi_hud_layer.py
  • tests/test_fsr3fi_hudless_colour.py
  • tests/test_fsr_image_retirement.py
  • tests/test_fsr_uniform_ownership.py
  • tests/test_game_menu_mouse_buttons.py
  • tests/test_guest_imported.py
  • tests/test_high_fps_fixes.py
  • tests/test_host_guest_writes.py
  • tests/test_hud_layout_row.py
  • tests/test_insn_fixed_convert.py
  • tests/test_job_queue.py
  • tests/test_libc_hooks.py
  • tests/test_lift_cache.py
  • tests/test_lift_lookups.py
  • tests/test_linux_preflight.py
  • tests/test_linux_pressure.py
  • tests/test_make_game_cache.py
  • tests/test_make_game_ngx.py
  • tests/test_mise_build.py
  • tests/test_missing_nup.py
  • tests/test_mods_list.py
  • tests/test_ngx_sdk.py
  • tests/test_pads_after_menu.py
  • tests/test_parallel_init_order.py
  • tests/test_pending_guest_import.py
  • tests/test_pipeline_play_cache.py
  • tests/test_portable_builder_home.py
  • tests/test_present_queue_default.py
  • tests/test_present_source_crop.py
  • tests/test_present_thread.py
  • tests/test_profiling_mode.py
  • tests/test_psychov35_fsr3_fg.py
  • tests/test_readback_timeout_source.py
  • tests/test_replay_write_order.py
  • tests/test_sdiv_overflow.py
  • tests/test_slow_frames.py
  • tests/test_song_note_cue.py
  • tests/test_spawn_emit.py
  • tests/test_staging_burst.py
  • tests/test_texel_buffer_ownership.py
  • tests/test_upscaler_rows.py
  • tests/test_vbytes.py
  • tests/test_vcore_escape.py
  • tests/test_vfpx_elem.py
  • tests/test_vk_occlusion_queries.py
  • tests/test_walk.py
  • tests/test_walk_key.py
  • tests/test_work_lock.py

Still to test:

  • By hand, build the host on Linux from a UTF-8 path and verify the build succeeds.
  • By hand, repeat the full game-free comparison on the rebased pair and name any failures reproduced on current main.
  • By hand, run a build's shader preparation on Linux or a different GPU driver and verify that the renderer ETA and saving status remain separate from build completion.

Measurements

Verdict: The renderer provides the measured countdown signal and distinguishes writing the cache from counting work. The raw renderer ETA is more responsive but less accurate overall on this cold trace, so the Launcher uses it as a bounded correction after its cumulative rate becomes available.

Setup: Windows 11 build 26300, i7-13700F, RTX 4070 driver 32.0.16.2101. Exact shared base and patched runtime, Most shader preparation, separate runtime caches. Launcher replay compares renderer ETA to the previous percentage-derived estimate on the same checkpoints.

Before: main @ 068fb8eb After: this PR @ 06cb158f (runtime @ 3d544fc7)
Shader ETA protocol events in real cold preparation 0 432, including 2 cache-saving events
Cold shader phase, one run per revision 714.39 s 689.32 s
Warm repetitions at Most 19.08 s, 30.64 s 23.73 s, 14.49 s
Shader ETA protocol in warm repetitions 0 events in each run 13 and 10 events, including 2 cache-saving events per run

On the patched run, the initial raw ETA at the 160 s checkpoint was 447 s against 530 s actual remaining. The cumulative estimate at the same point was 699 s. Across the 446 common one-second samples, mean absolute error was 49.68 s for cumulative progress and 88.23 s for raw renderer ETA. The Launcher bounds the renderer correction after cumulative evidence is available, lowering the mean error to 35.17 s on the same samples, while preserving explicit unknown and saving signals. The warm order was main, patch, patch, main. Both runtimes reused their own cache from the cold run. These timings describe the tested cases. Raw traces stay local.

A third patched preparation used a fresh configured driver-cache directory and kept the assembled runtime's application cache. It completed in 636.25 s with 595 ETA events including two saving events. The last 5% of reported work took 130.60 s, compared with 3.85 s in the original patched cold run. The Launcher tested a local late-rate adjustment on both traces and kept it out of the PR after it failed to improve the independent trace. A more accurate tail estimate needs measurements for the actual work groups and for the time workers spend draining.

Risks

The extra output is limited to the prepare-only renderer and is independent of compile progress. Older clients can ignore the added event. The existing LONGSHOT_PREPARE_ONLY switch keeps its default off for normal game startup. Reverting this change removes the extra event.

Checklist

Ready for review

  • One topic, on current main; the title is a Conventional Commit.
  • Tested on my own PC, in the game for a change the game runs, as Testing says.
  • mise run test passes (any failure that also fails on main is named). The earlier pair has a completed comparison. The current pair has focused checks and needs the full suite comparison.
  • Measured against main, or Measurements says why there is nothing to measure.
  • No game files, build output or hand-edited generated files; third_party/ untouched; nothing GPL-incompatible.

When it applies

  • A fix: a game-free test that fails on main and passes here.
  • A check under tests/ that reads changed source is updated, not weakened.
  • Host code builds on Windows (llvm-mingw) and Linux, with UTF-8 paths.
  • Docs updated.
  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.

Ready to merge

  • Everything in Still to test has run, its results in Tested.
  • Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers").
  • Approved in review, every comment answered.
  • CI passes on the head; on current main, measured again or a comment says why the numbers still hold.
## Summary The Launcher can only infer shader preparation time from an overall fraction. That fraction can jump when the renderer finds reusable work or changes from shader programs to pipelines. The prepare-only renderer now emits its own recent-rate estimate and clears it as the work changes or the pipeline cache is written. The producer is in `vk_progress.h` and `vk_main.cpp`. The existing saving intervals in `vk_draw.cpp` emit their status only in prepare-only mode. `make_game.py` forwards the new shader event and keeps the renderer's exit separate from the builder's completion. The Launcher consumer is [PR #213](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/213). ## Testing **Tested:** Windows 11 build 26300, NVIDIA RTX 4070 driver 32.0.16.2101. Both earlier exact runtimes completed real `--prepare-shaders` runs at Most. The patched renderer emitted 432 scoped signals, including two cache-saving events, and exited successfully. The relay regression failed on main because it stripped `@@shader_eta unknown` and passed on the patch. Five focused Windows checks passed after the first two assertions were updated. The test-only follow-up at `06cb158f` fixed the extracted prepare-cache and quit fixtures while preserving the renderer and builder source used by the game-tested runtime at `3d544fc7`. The interrupted Windows runner emitted `KeyboardInterrupt` and exited with Windows `STATUS_CONTROL_C_EXIT` (`0xC000013A`). Separate process groups completed all eight supported `tests/run_all.py --strict --shard K/8` shards. The exact base `068fb8eb` had 751 passes, 71 failures and 48 skips. The producer comparison had 752 passes, 70 failures and 48 skips across the same 870 checks. It reran the three shards containing the four changed fixture files and reused the results for the other, unchanged checks. The final revision also passed the tracked Python byte-compile check. `tests/test_prepare_cache_save.py` is the sole outcome that changed. The repaired fixture exercises the actual saving helper, checks its flag during the forced write, and verifies the `saving` and `unknown` events. Its Most refresh expectation now matches the renderer's existing progress calculation. A second matched run with the full repository-pinned Python packages, the supported llvm-mingw configuration and .NET 8 cleared `test_fpx_sticky.py`, `test_make_game_cache.py`, `test_portable_builder_home.py` and `test_walk.py` on both sides. **Rebase validation:** Replayed the published stack onto `89c3d21e`. Git's independent merge calculation matches `a74e3677` exactly. The relay regression failed at the test-only commit with the expected dropped `@@shader_eta unknown` signal. The rebased head passed all eight focused Windows checks and built the full Windows renderer with `dev.py vk`, including its export check. The latest main failed only the known Most-refresh expectation among the seven comparable focused tests. The 870-check comparison above applies to the earlier main and producer pair. The `Guide screenshots / Guide images and local UI source review` check reports the same 33 source-review items on current main and the rebased head. The Guide source review and its recorded hashes need attention on main for green merge CI. The two `CI / Python source checks (ubuntu-24.04, part 1/2)` and `CI / Python source checks (ubuntu-24.04, part 2/2)` jobs and `CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate)` are manual dispatch jobs. A Linux runner is still needed for the applicable host build and UTF-8 path checklist item. <details> <summary>70 named failures reproduced on the earlier main, 068fb8eb</summary> - `tests/test_appimage_player_build.py` - `tests/test_auto_handheld.py` - `tests/test_bug_report_defaults.py` - `tests/test_build_long_paths.py` - `tests/test_capture_read_once.py` - `tests/test_capture_readback_visibility.py` - `tests/test_crash_dialog.py` - `tests/test_crt_options.py` - `tests/test_damage_debug_menu.py` - `tests/test_dev_ab.py` - `tests/test_dev_build.py` - `tests/test_dev_migrate.py` - `tests/test_dev_packs.py` - `tests/test_discover.py` - `tests/test_display_startup_failure.py` - `tests/test_dlss_feature_size.py` - `tests/test_draw_stream_visibility.py` - `tests/test_failed_compile_keeps_objects.py` - `tests/test_fastfp_fma.py` - `tests/test_fma_soft.py` - `tests/test_fpx_sticky.py` - `tests/test_frame_overlap.py` - `tests/test_fsr3fi_hud_layer.py` - `tests/test_fsr3fi_hudless_colour.py` - `tests/test_fsr_image_retirement.py` - `tests/test_fsr_uniform_ownership.py` - `tests/test_game_menu_mouse_buttons.py` - `tests/test_guest_imported.py` - `tests/test_high_fps_fixes.py` - `tests/test_host_guest_writes.py` - `tests/test_hud_layout_row.py` - `tests/test_insn_fixed_convert.py` - `tests/test_job_queue.py` - `tests/test_libc_hooks.py` - `tests/test_lift_cache.py` - `tests/test_lift_lookups.py` - `tests/test_linux_preflight.py` - `tests/test_linux_pressure.py` - `tests/test_make_game_cache.py` - `tests/test_make_game_ngx.py` - `tests/test_mise_build.py` - `tests/test_missing_nup.py` - `tests/test_mods_list.py` - `tests/test_ngx_sdk.py` - `tests/test_pads_after_menu.py` - `tests/test_parallel_init_order.py` - `tests/test_pending_guest_import.py` - `tests/test_pipeline_play_cache.py` - `tests/test_portable_builder_home.py` - `tests/test_present_queue_default.py` - `tests/test_present_source_crop.py` - `tests/test_present_thread.py` - `tests/test_profiling_mode.py` - `tests/test_psychov35_fsr3_fg.py` - `tests/test_readback_timeout_source.py` - `tests/test_replay_write_order.py` - `tests/test_sdiv_overflow.py` - `tests/test_slow_frames.py` - `tests/test_song_note_cue.py` - `tests/test_spawn_emit.py` - `tests/test_staging_burst.py` - `tests/test_texel_buffer_ownership.py` - `tests/test_upscaler_rows.py` - `tests/test_vbytes.py` - `tests/test_vcore_escape.py` - `tests/test_vfpx_elem.py` - `tests/test_vk_occlusion_queries.py` - `tests/test_walk.py` - `tests/test_walk_key.py` - `tests/test_work_lock.py` </details> **Still to test:** - By hand, build the host on Linux from a UTF-8 path and verify the build succeeds. - By hand, repeat the full game-free comparison on the rebased pair and name any failures reproduced on current main. - By hand, run a build's shader preparation on Linux or a different GPU driver and verify that the renderer ETA and saving status remain separate from build completion. ## Measurements **Verdict:** The renderer provides the measured countdown signal and distinguishes writing the cache from counting work. The raw renderer ETA is more responsive but less accurate overall on this cold trace, so the Launcher uses it as a bounded correction after its cumulative rate becomes available. Setup: Windows 11 build 26300, i7-13700F, RTX 4070 driver 32.0.16.2101. Exact shared base and patched runtime, Most shader preparation, separate runtime caches. Launcher replay compares renderer ETA to the previous percentage-derived estimate on the same checkpoints. | | Before: main @ `068fb8eb` | After: this PR @ `06cb158f` (runtime @ `3d544fc7`) | |---|---|---| | Shader ETA protocol events in real cold preparation | 0 | 432, including 2 cache-saving events | | Cold shader phase, one run per revision | 714.39 s | 689.32 s | | Warm repetitions at Most | 19.08 s, 30.64 s | 23.73 s, 14.49 s | | Shader ETA protocol in warm repetitions | 0 events in each run | 13 and 10 events, including 2 cache-saving events per run | On the patched run, the initial raw ETA at the 160 s checkpoint was 447 s against 530 s actual remaining. The cumulative estimate at the same point was 699 s. Across the 446 common one-second samples, mean absolute error was 49.68 s for cumulative progress and 88.23 s for raw renderer ETA. The Launcher bounds the renderer correction after cumulative evidence is available, lowering the mean error to 35.17 s on the same samples, while preserving explicit unknown and saving signals. The warm order was main, patch, patch, main. Both runtimes reused their own cache from the cold run. These timings describe the tested cases. Raw traces stay local. A third patched preparation used a fresh configured driver-cache directory and kept the assembled runtime's application cache. It completed in 636.25 s with 595 ETA events including two saving events. The last 5% of reported work took 130.60 s, compared with 3.85 s in the original patched cold run. The Launcher tested a local late-rate adjustment on both traces and kept it out of the PR after it failed to improve the independent trace. A more accurate tail estimate needs measurements for the actual work groups and for the time workers spend draining. ## Risks The extra output is limited to the prepare-only renderer and is independent of compile progress. Older clients can ignore the added event. The existing `LONGSHOT_PREPARE_ONLY` switch keeps its default off for normal game startup. Reverting this change removes the extra event. ## Checklist ### Ready for review - [x] One topic, on current `main`; the title is a Conventional Commit. - [x] Tested on my own PC, in the game for a change the game runs, as Testing says. - [ ] `mise run test` passes (any failure that also fails on `main` is named). The earlier pair has a completed comparison. The current pair has focused checks and needs the full suite comparison. - [x] Measured against `main`, or Measurements says why there is nothing to measure. - [x] No game files, build output or hand-edited generated files; `third_party/` untouched; nothing GPL-incompatible. ### When it applies - [x] A fix: a game-free test that fails on `main` and passes here. - [x] A check under `tests/` that reads changed source is updated, not weakened. - [ ] Host code builds on Windows (llvm-mingw) and Linux, with UTF-8 paths. - [x] Docs updated. - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. ### Ready to merge - [ ] Everything in Still to test has run, its results in Tested. - [ ] Tier 1 hardware it can affect is tested (docs/dev/standards.md, "Hardware tiers"). - [ ] Approved in review, every comment answered. - [ ] CI passes on the head; on current `main`, measured again or a comment says why the numbers still hold.
Assisted-by: OpenAI Codex
fix(vk): report renderer shader countdown through make_game
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
CI / Conventional Commit title (pull_request) Successful in 7s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 10s
CI / Workflow lint (actionlint) (pull_request) Successful in 11s
Website / Website on Cloudflare (pull_request_target) Has been skipped
Third-party parts / As their notes say (pull_request) Successful in 12s
PR description / Description follows the template (pull_request_target) Successful in 3s
CI / Website build and checks (pull_request) Has been cancelled
3d544fc7d1
Assisted-by: OpenAI Codex
Author
Member

Tested in game: Windows 11 build 26300, RTX 4070 driver 32.0.16.2101. Both exact dev runtimes ran real Most shader preparation to exit 0. The patched renderer sent its scoped ETA and distinct cache-save status.

Tested in game: Windows 11 build 26300, RTX 4070 driver 32.0.16.2101. Both exact dev runtimes ran real Most shader preparation to exit 0. The patched renderer sent its scoped ETA and distinct cache-save status.
Member

Possibly related, for context:

  • issue #1178 Game: shader preparation takes hours on Iris Xe with Mesa on Debian — Slow shader-preparation ETA on Intel Linux
  • issue #1706 Install: Intel Arc A730 shader and pipeline preparation takes hours — Long shader-build preparation and unreliable countdown
  • PR #1174 WIP: fix(builder): a preparation the GPU driver stalled is not promised for the first start — Overlapping make_game.py builder status output
Possibly related, for context: - issue #1178 Game: shader preparation takes hours on Iris Xe with Mesa on Debian — Slow shader-preparation ETA on Intel Linux - issue #1706 Install: Intel Arc A730 shader and pipeline preparation takes hours — Long shader-build preparation and unreliable countdown - PR #1174 WIP: fix(builder): a preparation the GPU driver stalled is not promised for the first start — Overlapping make_game.py builder status output
Author
Member

Both warm repetitions passed on each exact runtime. The producer emitted separate saving events; replaying the same cold checkpoints shows the raw stage rate alone is too volatile, so the Launcher uses it as a bounded correction. Full Windows suite comparison is still running.

Both warm repetitions passed on each exact runtime. The producer emitted separate saving events; replaying the same cold checkpoints shows the raw stage rate alone is too volatile, so the Launcher uses it as a bounded correction. Full Windows suite comparison is still running.
Author
Member

The independent isolated shader run passed on the same producer head, with 595 ETA events and both saving notifications. The three focused strict checks passed again. The full Windows run stopped without a completed suite result, and the Guide checker reports the same 25 source-review issues on official main and this head.

The independent isolated shader run passed on the same producer head, with 595 ETA events and both saving notifications. The three focused strict checks passed again. The full Windows run stopped without a completed suite result, and the Guide checker reports the same 25 source-review issues on official main and this head.
test(vk): cover the shared shader saving helper
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
CI / Conventional Commit title (pull_request) Successful in 7s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 15s
CI / Website build and checks (pull_request) Has been cancelled
8adf89f576
Assisted-by: Codex
Author
Member

The interrupted Windows run returned STATUS_CONTROL_C_EXIT. Separate process groups completed all eight shards. Across the same 870 checks, main had 751 passes and 71 failures; the producer had 752 passes and 70 failures, all named and reproduced on main. The four repaired source checks and fixtures change only tests. Windows local validation is recorded, with the Linux host checklist and Guide merge check still open.

The interrupted Windows run returned STATUS_CONTROL_C_EXIT. Separate process groups completed all eight shards. Across the same 870 checks, main had 751 passes and 71 failures; the producer had 752 passes and 70 failures, all named and reproduced on main. The four repaired source checks and fixtures change only tests. Windows local validation is recorded, with the Linux host checklist and Guide merge check still open.
test(vk): exercise the saving helper in game-free fixtures
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
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
Third-party parts / As their notes say (pull_request) Successful in 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 34s
PR description / Description follows the template (pull_request_target) Successful in 3s
CI / Website build and checks (pull_request) Has been cancelled
06cb158fa8
Assisted-by: Codex
futondestroyer force-pushed fix/renderer-shader-eta from 06cb158fa8
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
CI / Conventional Commit title (pull_request) Successful in 8s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 11s
Third-party parts / As their notes say (pull_request) Successful in 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 34s
PR description / Description follows the template (pull_request_target) Successful in 3s
CI / Website build and checks (pull_request) Has been cancelled
to a74e36773a
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 9s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 13s
CI / Website build and checks (pull_request) Failing after 1m49s
2026-11-20 12:38:14 +00:00
Compare
Author
Member

Rebased on 89c3d21e. The relay test fails for the expected missing event on the test-only commit, all eight focused Windows checks pass on the head, and the renderer builds and passes its export check. The prior full Windows comparison remains recorded for its exact pair. The current full suite and Linux host check remain open.

Rebased on 89c3d21e. The relay test fails for the expected missing event on the test-only commit, all eight focused Windows checks pass on the head, and the renderer builds and passes its export check. The prior full Windows comparison remains recorded for its exact pair. The current full suite and Linux host check remain open.
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 9s
PR description / Description follows the template (pull_request_target) Successful in 10s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 12s
CI / Workflow lint (actionlint) (pull_request) Successful in 12s
Third-party parts / As their notes say (pull_request) Successful in 13s
CI / Website build and checks (pull_request) Failing after 1m49s
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u 'fix/renderer-shader-eta:futondestroyer-fix/renderer-shader-eta'
git switch 'futondestroyer-fix/renderer-shader-eta'
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!1830
No description provided.