Repository navigation
ci: fix Models Backend by shortening the hrm_text fixture - #29744
Merged
Merged
Conversation
The fixture recycles its two blocks over 8 cache slots, so the fp16 error builds up past the 1e-4 NMSE bound on the Vulkan T4 and WebGPU jobs of Models Backend. Two l-cycles keep every branch of the cycle loop and halve the error.
Contributor
Author
|
Measured on an RTX PRO 6000, where the values differ from the CI GPUs, but the error scales with the depth so the CI should drop by the same ratio. The Models Backend run on this PR will confirm. |
Member
|
cc/ @jeffbolznv |
pierreguillot
pushed a commit
to Ircam-Partiels/llama.cpp
that referenced
this pull request
Oct 1, 2026
…l-org#29744) The fixture recycles its two blocks over 8 cache slots, so the fp16 error builds up past the 1e-4 NMSE bound on the Vulkan T4 and WebGPU jobs of Models Backend. Two l-cycles keep every branch of the cycle loop and halve the error.
frostyautumnleaf
pushed a commit
to frostyautumnleaf/llama.cpp
that referenced
this pull request
Oct 5, 2026
…l-org#29744) The fixture recycles its two blocks over 8 cache slots, so the fp16 error builds up past the 1e-4 NMSE bound on the Vulkan T4 and WebGPU jobs of Models Backend. Two l-cycles keep every branch of the cycle loop and halve the error.
edwardyoon
pushed a commit
to edwardyoon/focus-llama
that referenced
this pull request
Oct 7, 2026
…l-org#29744) The fixture recycles its two blocks over 8 cache slots, so the fp16 error builds up past the 1e-4 NMSE bound on the Vulkan T4 and WebGPU jobs of Models Backend. Two l-cycles keep every branch of the cycle loop and halve the error. (cherry picked from commit 3b3d022)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Fix CI:
The new Models Backend check is red on every run because of hrm_text: it lands just above the 1e-4 bound on Vulkan (1.10e-04) and WebGPU (1.53e-04), same numbers every time.
The bound is fine, the hrm_text test model is just too deep for it. HRM reuses its layers in cycles, and our fixture runs them through 8 passes where most archs have 2. Each pass adds a bit of fp16 rounding, so it ends up about 10x noisier than any other arch. With f16 disabled it drops to 3.5e-10, so nothing is wrong in the model itself.
This PR makes the fixture a bit shorter: 6 passes instead of 8. It still goes through every branch of the cycle loop, and the error roughly halves.
NMSE over 5 seeds on an RTX PRO 6000:
Additional information
Follow-up #29651 cc @CISC
Requirements