fix(vk): anchor program life events to the host trace #239

Open
klimovich008 wants to merge 6 commits from klimovich008/Longshot:codex/program-life-clock387 into main
Contributor

Type: fix · Risk: low · Tested on: Windows 11, RX 9070 XT; Linux, RTX 4090 (DuckNintendo) · Needs: Linux, any GPU: clock/frame alignment (T-3VG4)

Why

With RX_VK_LOG_PROGRAM_LIFE=1 the renderer logs when each program is made, first drawn and freed, but those times run on their own clock, so they can't be matched to the frames in a HOS_PRESENT_TRACE trace: you can't tell which frame a slow first draw landed in. This adds one clock anchor that bridges the two. The tracker was searched (forge.py issue list); no issue covers it.

How to reproduce

Seen on: any OS and GPU
Settings and switches: RX_VK_LOG_PROGRAM_LIFE=1
Steps: play a minute on main, then look for a line that relates the program-life times to the host clock in longshot_log.txt
Expected: a reference point to convert a program-life time into a host-trace time
Actual: none: the program-life t values are seconds since the renderer's own start, with nothing tying them to the host clock

What changed

Once the host is bound, the program-life log prints one anchor line: two host-clock readings bracketing one program-life clock reading. Off by default; with the switch off nothing is read.

  • gpu/vk/vk_programs.cpp: the anchor (host_before_ns, life_ns, host_after_ns), taken once after host binding; a call before the host is bound leaves it for later.
  • tests/test_program_life_clock.py (new): the real function cut from the source, off/on/before-init.
  • docs/development.md: how to convert a program-life t to the host clock with the anchor (the 0.5 ms rounding allowance); two docs/tested/ run files.

Measurements

Verdict: the anchor works (one line a run with the switch on, none off, on Windows AMD and Linux NVIDIA); no performance effect claimed: the A/B's difference comes from the control runs' stalls.

Hardware: Windows 11, RX 9070 XT, AMD 26.10.2, Ryzen 7 5700X3D, 64 GB
Scene: Hyrule Field (the standard test's save), camera turning at full speed; 1280x720 window (16:9), fixed Custom profile, no upscaler, no frame generation, HOS_FPS_MAX=240
Method: the standard test (std_test.py) with RX_VK_LOG_PROGRAM_LIFE=1 on both arms, 20 s windows, 3 alternating pairs without warm-ups; pair 3 skipped (its control's game clock was 0.946 inside the window, during a 277 ms frame), so 2 valid pairs; the median; clock lines counted in each run's log.
How to reproduce: set RX_VK_LOG_PROGRAM_LIFE=1, load the save, turn the camera; grep "program life: clock" longshot_log.txt
Baseline: this PR measured as its code and test on main 839e85ff (f50a8d3d, a renderer-only pack, docs left out).

Before: main @ 839e85ff After: this PR @ 9b8287e6
fps, runs (median) 63.09, 61.09 (62.09) 63.73, 64.29 (64.01)
CPU ms a frame, median 64.87 61.66
worst frame 372, 452 ms 122, 61 ms
clock anchor lines a run 0 1
vk: program life: clock host_before_ns 74961421584744 life_ns 128807893 host_after_ns 74961421584864   (DuckNintendo, Linux)

Flags and settings

None new. The existing RX_VK_LOG_PROGRAM_LIFE=1 stays off by default; with it on, it now also prints the anchor.

Testing

Tested:

  • tests/test_program_life_clock.py: off, on and before host binding; fails on main (no anchor), passes here. Windows (llvm-mingw clang) and Linux (clang 21, WSL).
  • python -I -B tests/run_all.py --jobs 4 on this branch with main 71b1edd8 merged: 608 passed, 25 failed, 45 skipped; the same 25 fail on clean main 71b1edd8 on this PC (607 passed there: this PR adds one test), among them test_vk_occlusion_queries.py, test_walk_key.py and test_crash_dialog.py
  • Linux (WSL Ubuntu): vk_programs.cpp compiled to an object with clang 21 and the build's Linux flags.
  • In the game, Windows RX 9070 XT: the A/B above. Linux, RTX 4090, NVIDIA (DuckNintendo, PR head 3ebdf864): exactly one clock line right after the renderer starts, bracketing 120 ns; 17,497 program-life lines as before; none of either with the switch off; no error or validation lines; 59.1 fps median at the 60 cap. Code review: bibiburl (no defect).

Not tested: matching program-life events to HOS_PRESENT_TRACE frame intervals on a real run.

Must be tested:

  • Linux, any GPU: run with RX_VK_LOG_PROGRAM_LIFE=1 and HOS_PRESENT_TRACE, convert a few first-draw times with the anchor and the documented 0.5 ms allowance, expecting each to fall inside a frame interval of the trace (Test Farm: @Beanstalk request on this PR, linux, for the one clock line and no errors; the conversion against the trace by hand: test request T-3VG4)

Risks

What could break: nothing with the switch off (no clock is read); with it on, one extra log line.

Turning it off: leave RX_VK_LOG_PROGRAM_LIFE unset (the default), or revert the commit.

Compatibility: Nothing changes.

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).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • 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.
  • A file in docs/tested/ for each new measured run (format in docs/tested-configurations.md).
  • A game-free test added for the fix, failing on main and passing here.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths.
  • Docs updated.

🤖 Generated with Claude Code

**Type:** fix · **Risk:** low · **Tested on:** Windows 11, RX 9070 XT; Linux, RTX 4090 (DuckNintendo) · **Needs:** Linux, any GPU: clock/frame alignment (T-3VG4) ## Why With `RX_VK_LOG_PROGRAM_LIFE=1` the renderer logs when each program is made, first drawn and freed, but those times run on their own clock, so they can't be matched to the frames in a `HOS_PRESENT_TRACE` trace: you can't tell which frame a slow first draw landed in. This adds one clock anchor that bridges the two. The tracker was searched (`forge.py issue list`); no issue covers it. ## How to reproduce **Seen on:** any OS and GPU **Settings and switches:** `RX_VK_LOG_PROGRAM_LIFE=1` **Steps:** play a minute on main, then look for a line that relates the program-life times to the host clock in `longshot_log.txt` **Expected:** a reference point to convert a program-life time into a host-trace time **Actual:** none: the program-life `t` values are seconds since the renderer's own start, with nothing tying them to the host clock ## What changed Once the host is bound, the program-life log prints one anchor line: two host-clock readings bracketing one program-life clock reading. Off by default; with the switch off nothing is read. - `gpu/vk/vk_programs.cpp`: the anchor (`host_before_ns`, `life_ns`, `host_after_ns`), taken once after host binding; a call before the host is bound leaves it for later. - `tests/test_program_life_clock.py` (new): the real function cut from the source, off/on/before-init. - `docs/development.md`: how to convert a program-life `t` to the host clock with the anchor (the 0.5 ms rounding allowance); two `docs/tested/` run files. ## Measurements **Verdict:** the anchor works (one line a run with the switch on, none off, on Windows AMD and Linux NVIDIA); no performance effect claimed: the A/B's difference comes from the control runs' stalls. Hardware: Windows 11, RX 9070 XT, AMD 26.10.2, Ryzen 7 5700X3D, 64 GB Scene: Hyrule Field (the standard test's save), camera turning at full speed; 1280x720 window (16:9), fixed Custom profile, no upscaler, no frame generation, `HOS_FPS_MAX=240` Method: the standard test (std_test.py) with `RX_VK_LOG_PROGRAM_LIFE=1` on both arms, 20 s windows, 3 alternating pairs without warm-ups; pair 3 skipped (its control's game clock was 0.946 inside the window, during a 277 ms frame), so 2 valid pairs; the median; clock lines counted in each run's log. How to reproduce: set `RX_VK_LOG_PROGRAM_LIFE=1`, load the save, turn the camera; `grep "program life: clock" longshot_log.txt` Baseline: this PR measured as its code and test on main 839e85ff (f50a8d3d, a renderer-only pack, docs left out). | | Before: main @ 839e85ff | After: this PR @ 9b8287e6 | |---|---|---| | fps, runs (median) | 63.09, 61.09 (62.09) | 63.73, 64.29 (64.01) | | CPU ms a frame, median | 64.87 | 61.66 | | worst frame | 372, 452 ms | 122, 61 ms | | clock anchor lines a run | 0 | 1 | ``` vk: program life: clock host_before_ns 74961421584744 life_ns 128807893 host_after_ns 74961421584864 (DuckNintendo, Linux) ``` ### Flags and settings None new. The existing `RX_VK_LOG_PROGRAM_LIFE=1` stays off by default; with it on, it now also prints the anchor. ## Testing **Tested:** - `tests/test_program_life_clock.py`: off, on and before host binding; fails on main (no anchor), passes here. Windows (llvm-mingw clang) and Linux (clang 21, WSL). - `python -I -B tests/run_all.py --jobs 4` on this branch with main 71b1edd8 merged: 608 passed, 25 failed, 45 skipped; the same 25 fail on clean main 71b1edd8 on this PC (607 passed there: this PR adds one test), among them `test_vk_occlusion_queries.py`, `test_walk_key.py` and `test_crash_dialog.py` - Linux (WSL Ubuntu): `vk_programs.cpp` compiled to an object with clang 21 and the build's Linux flags. - In the game, Windows RX 9070 XT: the A/B above. Linux, RTX 4090, NVIDIA (DuckNintendo, PR head 3ebdf864): exactly one clock line right after the renderer starts, bracketing 120 ns; 17,497 program-life lines as before; none of either with the switch off; no error or validation lines; 59.1 fps median at the 60 cap. Code review: bibiburl (no defect). **Not tested:** matching program-life events to `HOS_PRESENT_TRACE` frame intervals on a real run. **Must be tested:** - Linux, any GPU: run with `RX_VK_LOG_PROGRAM_LIFE=1` and `HOS_PRESENT_TRACE`, convert a few first-draw times with the anchor and the documented 0.5 ms allowance, expecting each to fall inside a frame interval of the trace (Test Farm: `@Beanstalk` request on this PR, linux, for the one clock line and no errors; the conversion against the trace by hand: test request T-3VG4) ## Risks **What could break:** nothing with the switch off (no clock is read); with it on, one extra log line. **Turning it off:** leave `RX_VK_LOG_PROGRAM_LIFE` unset (the default), or revert the commit. **Compatibility:** Nothing changes. ## 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] Measurements has a verdict, or one line saying why there is nothing to measure. - [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. - [x] A file in `docs/tested/` for each new measured run (format in `docs/tested-configurations.md`). - [x] A game-free test added for the fix, failing on `main` and passing here. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Host code builds on both Windows (llvm-mingw) and Linux, with UTF-8 paths. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Program-life events use a DLL-relative clock, so their times cannot be
joined directly to a host present trace. Log one relative sample bracketed
by the existing host clock when the diagnostic is first enabled. Keep
logging off by default and preserve the renderer API and shader caches.

The real-function C++ fixture fails on the old code and passes here. It
checks disabled logging, one-time emission, clock order and integer values.
Full source checks and a matched game capture are still pending.

Assisted-by: OpenAI Codex
Assisted-by: GPT-6.1 Sol
Co-Authored-By: OpenAI Codex <[email protected]>
Co-Authored-By: GPT-6.1 Sol <[email protected]>
fix(vk): defer the life clock until the host is bound
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
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
1fea819e7c
Failed renderer initialization can reach the close census before host is
assigned. Skip the diagnostic until a host exists, outside the static
initializer so a later valid initialization can still enable it.

The real-function fixture now checks early calls and a later valid host.
It fails on the unguarded clock change and passes with the guard; the
normal on and off cases still pass.

Assisted-by: OpenAI Codex
Assisted-by: GPT-6.1 Sol
Co-Authored-By: OpenAI Codex <[email protected]>
Co-Authored-By: GPT-6.1 Sol <[email protected]>
Author
Contributor

Description only: the Flags and settings table and the source-reading test box filled in; no source change (still 1fea819e). Stays WIP.

Description only: the Flags and settings table and the source-reading test box filled in; no source change (still 1fea819e). Stays WIP.
Author
Contributor

Refreshed the unchanged real-function fixture: PR 1fea819e passes off/on/pre-host cases; pinned main 5b81a8a1 fails the anchor check. Historical suite and earlier backport gameplay are labelled separately. Final-DLL gameplay, measurement, Linux and test requests remain open. This stays WIP.

Refreshed the unchanged real-function fixture: PR 1fea819e passes off/on/pre-host cases; pinned main 5b81a8a1 fails the anchor check. Historical suite and earlier backport gameplay are labelled separately. Final-DLL gameplay, measurement, Linux and test requests remain open. This stays WIP.
klimovich008 force-pushed codex/program-life-clock387 from 1fea819e7c
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
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 8892a8de62
Some checks failed
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
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
2026-11-14 14:45:31 +00:00
Compare
Author
Contributor

Rebased linearly onto main 5e072fc8 (Codex: 9b4e2c3c, f8ee4f8a; same code), plus the run records (8892a8de). The fixture fails on main and passes here; full suite 517/9/36 with the same 9 failures as clean main. Measured: the standard test with RX_VK_LOG_PROGRAM_LIFE=1 on both arms, 2 valid pairs (pair 3 skipped for the control's clock), one clock-anchor line per PR run and none on main, no speed-up claimed. Linux: object and fixture with clang 21; the full Linux build is T-3VG4. Taking it out of WIP.

Rebased linearly onto main 5e072fc8 (Codex: 9b4e2c3c, f8ee4f8a; same code), plus the run records (8892a8de). The fixture fails on main and passes here; full suite 517/9/36 with the same 9 failures as clean main. Measured: the standard test with RX_VK_LOG_PROGRAM_LIFE=1 on both arms, 2 valid pairs (pair 3 skipped for the control's clock), one clock-anchor line per PR run and none on main, no speed-up claimed. Linux: object and fixture with clang 21; the full Linux build is T-3VG4. Taking it out of WIP.
klimovich008 changed title from WIP: fix(vk): anchor program life events to the host trace to fix(vk): anchor program life events to the host trace 2026-11-14 14:46:10 +00:00
docs(tested): #239's control run: the rejecting clock reading was 0.946 inside the window
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 28s
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
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
9b8287e69c
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Contributor

Correction, description and run record only (9b8287e6): pair 3's control was rejected on a 0.946 clock reading inside the window (during a 277 ms frame), not the 0.761 edge reading I quoted, which the acceptance does not use (Codex caught it). The accepted pairs and numbers are unchanged.

Correction, description and run record only (9b8287e6): pair 3's control was rejected on a 0.946 clock reading inside the window (during a 277 ms frame), not the 0.761 edge reading I quoted, which the acceptance does not use (Codex caught it). The accepted pairs and numbers are unchanged.
Merge main 543846eb into codex/program-life-clock387
Some checks failed
PR description / Description follows the template (pull_request_target) Successful in 18s
Website / Website on Cloudflare (pull_request_target) Has been skipped
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
Third-party parts / As their notes say (pull_request) Has been cancelled
Third-party parts / The same as upstream (pull_request) Has been cancelled
Website / Website on Cloudflare (pull_request) Has been cancelled
3ebdf864ff
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Contributor

Merged main 543846eb (3ebdf864, no force-push): the only conflict was docs/development.md, where main added the GPU-wait paragraph next to this PR's clock-anchor paragraph; both are kept. tests/test_program_life_clock.py and test_check_pr_description.py pass on the merge; the full suite follows.

Merged main 543846eb (3ebdf864, no force-push): the only conflict was docs/development.md, where main added the GPU-wait paragraph next to this PR's clock-anchor paragraph; both are kept. tests/test_program_life_clock.py and test_check_pr_description.py pass on the merge; the full suite follows.
Author
Contributor

Full suite on the merge (3ebdf864, main 543846eb, Windows, llvm-mingw 20261104, --jobs 4): 533 passed, 3 failed, 36 skipped. The same 3 fail on clean main 543846eb here (532/3/36): tests/test_oot_state_tap.py, tests/test_tested_configurations.py, tests/test_walk_key.py.

Full suite on the merge (3ebdf864, main 543846eb, Windows, llvm-mingw 20261104, --jobs 4): 533 passed, 3 failed, 36 skipped. The same 3 fail on clean main 543846eb here (532/3/36): tests/test_oot_state_tap.py, tests/test_tested_configurations.py, tests/test_walk_key.py.
Member

Code-only review of 3ebdf864ff; informational findings, with final approval left to another reviewer.

No introduced correctness defect found in the clock-anchor change. The host readings bracket the same relative clock used by the life events, integer formatting preserves the timestamps, and an early call before host binding leaves initialization available for the later valid call. Logging disabled adds no clock reads.

The extracted-function fixture checks off/on/pre-host behavior, sample order, one-time logging and large integer timestamps; removing the anchor or caching the pre-host result would fail it. It does not establish alignment between the real platform clocks and the linked game's frame trace. The recorded Windows renderer-backport runs provide one anchor per run, with no speed-up claimed; Linux object compilation and the fixture are narrower evidence. The existing Linux clock/frame-alignment request T-3VG4 remains the validation gap: record an enabled run and match life events to host frame intervals using the documented bracket and 0.5 ms rounding allowance.

I read the full diff, initialization/logging call paths, clock implementation, fixture and reported runs. The other open changes to vk_programs.cpp touch different functions; no required merge order found. No builds, tests or game runs performed in this review.

Code-only review of 3ebdf864ff9fa1ed6f1364d0fb193f68264c4829; informational findings, with final approval left to another reviewer. No introduced correctness defect found in the clock-anchor change. The host readings bracket the same relative clock used by the life events, integer formatting preserves the timestamps, and an early call before host binding leaves initialization available for the later valid call. Logging disabled adds no clock reads. The extracted-function fixture checks off/on/pre-host behavior, sample order, one-time logging and large integer timestamps; removing the anchor or caching the pre-host result would fail it. It does not establish alignment between the real platform clocks and the linked game's frame trace. The recorded Windows renderer-backport runs provide one anchor per run, with no speed-up claimed; Linux object compilation and the fixture are narrower evidence. The existing Linux clock/frame-alignment request **T-3VG4** remains the validation gap: record an enabled run and match life events to host frame intervals using the documented bracket and 0.5 ms rounding allowance. I read the full diff, initialization/logging call paths, clock implementation, fixture and reported runs. The other open changes to `vk_programs.cpp` touch different functions; no required merge order found. No builds, tests or game runs performed in this review.
First-time contributor

Test request T-3VG4 — independent check. The card is not claimable yet (#239 is not from a collaborator and has no testing wanted label), so this is not a claim and the request stays open.

Linux, NVIDIA RTX 4090 24 GB, NVIDIA proprietary Vulkan driver. PR head 3ebdf864 (a merge of main 543846eb), built from the branch.

Unit test: tests/test_program_life_clock.py: PASS clock anchor off, PASS clock anchor on, PASS clock anchor before-init.

With RX_VK_LOG_PROGRAM_LIFE=1 (saved spot, Hyrule Field, about 70 s, then the window closed):

vk: program life: clock host_before_ns 74961421584744 life_ns 128807893 host_after_ns 74961421584864

Exactly one clock line, right after the renderer starts, and it brackets a 128.8 ms window (host_before_ns and host_after_ns differ by 120 ns).

The program-life lines are as before: 17497 lines in the run, 15753 create, 924 first draw, 315 first dispatch, each with its serial, time, frame, kind, stages, codes and timings. No error or validation lines.

Without the switch, the same run: 0 clock lines, 0 program-life lines anywhere in the log.

Both runs reached Hyrule Field and held the 60 fps cap (59.1 fps median); the switch adds logging only.

The request also says 'program-life lines as before': I did not build main to compare, but the merge with main adds no change to those lines.

Generated by opencode with deepseek-v4.1-flash-1017

Test request T-3VG4 — independent check. The card is not claimable yet (#239 is not from a collaborator and has no `testing wanted` label), so this is not a claim and the request stays open. Linux, NVIDIA RTX 4090 24 GB, NVIDIA proprietary Vulkan driver. PR head `3ebdf864` (a merge of main `543846eb`), built from the branch. **Unit test:** `tests/test_program_life_clock.py`: `PASS clock anchor off`, `PASS clock anchor on`, `PASS clock anchor before-init`. **With `RX_VK_LOG_PROGRAM_LIFE=1`** (saved spot, Hyrule Field, about 70 s, then the window closed): ``` vk: program life: clock host_before_ns 74961421584744 life_ns 128807893 host_after_ns 74961421584864 ``` Exactly one clock line, right after the renderer starts, and it brackets a 128.8 ms window (host_before_ns and host_after_ns differ by 120 ns). The program-life lines are as before: 17497 lines in the run, 15753 `create`, 924 `first draw`, 315 `first dispatch`, each with its serial, time, frame, kind, stages, codes and timings. No error or validation lines. **Without the switch**, the same run: 0 clock lines, 0 program-life lines anywhere in the log. Both runs reached Hyrule Field and held the 60 fps cap (59.1 fps median); the switch adds logging only. The request also says 'program-life lines as before': I did not build main to compare, but the merge with main adds no change to those lines. Generated by opencode with deepseek-v4.1-flash-1017
Merge main 71b1edd8 into codex/program-life-clock387
Some checks are pending
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
beanstalk/approval waiting for a BigBean's 👍 on the request
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
66af3067fe
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Author
Contributor

Merged main 71b1edd8 (66af3067, a fast-forward, no force-push) and rewrote the description in the new template.

  • Full suite on the merge (Windows, llvm-mingw 20261104, --jobs 4): 608 passed, 25 failed, 45 skipped. The same 25 fail on clean main 71b1edd8 on this PC (607 passed there; this PR adds tests/test_program_life_clock.py).
  • Thanks @DuckNintendo for the Linux RTX 4090 run: it is in Testing and the status line (one clock line, 120 ns bracket, none with the switch off). T-3VG4 stays open for the trace alignment check.
  • Thanks @bibiburl for the code review (no defect); the platform-clock alignment it leaves open is the Must be tested item.
  • A Test Farm request for the log check follows in the next comment.
Merged main 71b1edd8 (66af3067, a fast-forward, no force-push) and rewrote the description in the new template. - Full suite on the merge (Windows, llvm-mingw 20261104, `--jobs 4`): 608 passed, 25 failed, 45 skipped. The same 25 fail on clean main 71b1edd8 on this PC (607 passed there; this PR adds `tests/test_program_life_clock.py`). - Thanks @DuckNintendo for the Linux RTX 4090 run: it is in Testing and the status line (one clock line, 120 ns bracket, none with the switch off). T-3VG4 stays open for the trace alignment check. - Thanks @bibiburl for the code review (no defect); the platform-clock alignment it leaves open is the Must be tested item. - A Test Farm request for the log check follows in the next comment.
Author
Contributor

@Beanstalk linux, any GPU: with RX_VK_LOG_PROGRAM_LIFE=1 on both sides, 60 s in Hyrule Field. On the PR side expect exactly one "vk: program life: clock" line in the log (main has none), and no crash or error lines on either side.

@Beanstalk linux, any GPU: with RX_VK_LOG_PROGRAM_LIFE=1 on both sides, 60 s in Hyrule Field. On the PR side expect exactly one "vk: program life: clock" line in the log (main has none), and no crash or error lines on either side.
Member

@klimovich008 only members of BigBeans can start the farm. One of them can approve this request by reacting 👍 to it.

@klimovich008 only members of `BigBeans` can start the farm. One of them can approve this request by reacting 👍 to it.
Some checks are pending
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
beanstalk/approval waiting for a BigBean's 👍 on the request
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Successful in 6s
This pull request has changes conflicting with the target branch.
  • docs/development.md
Some workflows are waiting to be reviewed.
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 'codex/program-life-clock387:klimovich008-codex/program-life-clock387'
git switch 'klimovich008-codex/program-life-clock387'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 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!239
No description provided.