Repository navigation
t27b ledger: bless from master a7fa547a6, two reference-bug rows, cap 144 -> 125 (Closes #11924) - #11925
Merged
Conversation
…ap 144 -> 125 (Closes #11924) The ledger came from d800c56. It did not name 56 specs that have landed since, so master t27b native was red. Every PR was also red in --pr mode on a jit/interp mismatch in a file it does not touch: #11920 on frame_render, #11922 on lanes_view. Each fix was held red by the other one. Both mismatches are defects in the specs: the tests read bytes they never wrote. They go in by hand with reason reference-bug, as the bless refusal asks. Source: artifact t27b-native-run of run 40038516068. Ratchet with the new ledger: master run green (all counts 0); --pr on 668f73b (#11922) and on 1d4325b (#11920) green. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
This was referenced Oct 24, 2026
Closed
Summary by t27-beesThis PR updates the t27b expectations ledger to a new baseline from master commit a7fa547. The cap for allowed non-passing specs drops from 144 to 125, many previously blocked specs now pass, and two specs are explicitly marked as Worth a look
Read: 1 files, +89 -33, the whole diff. Head |
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.
Closes #11924
docs/reports/t27b_expectations.jsonis blessed from thet27b-native-runartifact of master run 40038516068 (a7fa547). That is the same chore as #11723. Master tip 3e47410 differs from a7fa547 only in seals.--prmode on a mismatch in a file it does not touch. fix(t27os): lv_copy_row copies the row's written bytes, not the dead tail (Closes #11919) #11920 fixes lanes_view and is red only on frame_render. test(t27f): frame_render clears the raster before it blends (Refs #3) #11922 fixes frame_render and is red only on lanes_view. Each PR held the other one red.reference-bug:specs/t27f/frame_render.t27andspecs/t27os/lanes_view.t27. In both, the test reads bytes it never wrote, t27c passes by luck, and t27b's interpreter correctly faults. The bless refused these two rows without a reason and asked for this one.Ratchet checked with the new ledger against the three CI artifacts:
--pr--prOnce #11920 and #11922 land, master shows UNEXPECTED PASS on those two rows until the next bless. That means the ledger is behind, not that something regressed.
No spec changed, so there is no t27c/t27b leg to run. Both compilers' verdicts are the ones in the master run artifact.
🤖 Generated with Claude Code