Repository navigation
conformance: the gate's total is 24,106, and +404 of the jump is the measurement - #54
Merged
Merged
Conversation
…measurement go-embedded-ruby/ruby#961 re-recorded BASELINE on the pinned runner; it now sums to 24,106. This site's own check (tools/conformancefigure, docs.yml) reads that file from ruby's main and was RED from the merge on: 5 claims, all reading 23,672. _index.md:13 the front page conformance.md:165 the callout title conformance.md:217 "The sum is ..." conformance.md:354 the end of the climb from 6 000 roadmap.md:22 "its sum is ..." ⭐ "NOT EVERY GAIN IS VM CONFORMANCE" NOW LISTS THREE. That section exists to keep fixes to the measurement apart from fixes to the interpreter, and it ended "The rest of the climb is the VM" -- which stopped being true today. The shim's platform guards compared `pointer_size: 64` against a size in bytes, so every such guard was shut on every machine; two files counted at 0 measured 188 and 216 with only the shim changed, and on the pinned runner the fix is +404 of the day's +434 (main alone read 23 702). A third bullet says so, with the files, and also that the fix REMOVED darwin expectations the old list had been counting as linux passes -- a gain in what is seen is not always a gain in the count. ⛔ AND A TRANSCRIPT NO GATE READS. conformance.md:182-185 shows $ awk ... scripts/conformance/rubyspec/BASELINE 23673 as the figure "read straight out of the gate's own file". The tool does not match it -- it is a command's output, not a sentence -- and it was ALREADY wrong by one: 23673 is the sum from before 2026-11-04, when core/random/bytes_spec.rb's row was pinned from 9 to its floor of 8. Nothing has refreshed it since, which is the proof that nothing reads it. Updated to 24106 here; a transcript of that command is a claim in everything but grammar, and the vocabulary should learn it. CONTROL: the lane's own command, `go run ./tools/conformancefigure --root content/en`, run on this tree against ruby's main: 5 claims before, 5 after, passing. The count is the evidence -- a rewording that took a claim out of the vocabulary would have checked 4 and passed just the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The gate's total is 24,106 — and this site's own check was red until it said so
go-embedded-ruby/ruby#961 re-recorded
BASELINEon the pinned runner; it sums to 24,106.tools/conformancefigure(thedocs.ymlstep) reads that file from ruby'smain, so from that merge on it failed here on 5 claims, all reading 23,672.content/en/_index.md:13content/en/conformance.md:165content/en/conformance.md:217content/en/conformance.md:354content/en/roadmap.md:22⭐ "Not every gain is VM conformance" now lists three
That section exists to keep fixes to the measurement apart from fixes to the interpreter, and it ended "The rest of the climb is the VM" — which stopped being true today. The shim's platform guards compared
pointer_size: 64against a size in bytes, so every such guard was shut on every machine: two files counted at 0 measured 188 and 216 with only the shim changed, and on the pinned runner the fix is +404 of the day's +434 (main alone read 23 702). A third bullet says so — and also that the fix removed darwin expectations the old list had been counting as linux passes.⛔ A transcript no gate reads
conformance.md:182-185showsawk … BASELINEprinting 23673, as the figure "read straight out of the gate's own file". The tool does not match it — it is a command's output, not a sentence — and it was already wrong by one before today: 23 673 is the sum from before 2026-11-04, whencore/random/bytes_spec.rb's row was pinned from 9 to its floor of 8. Nothing has refreshed it since, which is the proof nothing reads it. Updated here; a transcript of that command is a claim in everything but grammar, and the tool's vocabulary should learn the shape.Control
The lane's own command, on this tree, against ruby's
main:5 claims before the edit, 5 after. ⛔ The count is the evidence: a rewording that took a claim out of the vocabulary would have checked 4 and passed just the same.
Refs go-embedded-ruby/ruby#961, go-embedded-ruby/ruby#837 — both closed; named for where the figure comes from.
🤖 Generated with Claude Code