Repository navigation
landing: this page states two counts of one thing, and the stale one is undated - #43
Merged
Merged
Conversation
…is undated `hugo.toml:74` says 2,202 of 2,206 spec files produce a result, "the other 4 recorded as FILEFAIL". `layouts/_default/list.html:78` says "10 of 2,206 spec files produce no result". Same site, same corpus, both in the present tense, 4 against 10. Derived from the record CI actually enforces -- `scripts/conformance/rubyspec/BASELINE` on the ruby repository's main -- there are **4** FILEFAIL rows. hugo.toml is right; list.html carries the 2026-09-26 run's figure, two months old. ⛔ The fix is NOT to change 10 into 4. That whole sentence is one dated run: "93.3% pass (22,488 of 24,116); 477 more are skipped ... 10 of 2,206 produce no result". Dropping a November count into a September sentence makes the paragraph internally inconsistent while every individual number looks defensible -- the shape where two errors cancel and nothing shows it. So the run is NAMED, the sentence is left as that run's shape, and the current baseline count is stated beside it with the reason. ⛔ Counting FILEFAIL needed care, which is worth recording: `grep -c FILEFAIL BASELINE` answers **5**, because line 2 is the header comment that EXPLAINS the FILEFAIL format. Reading the matching lines instead of trusting the count gives 4 -- at core/kernel/exit_spec.rb, core/mutex/lock_spec.rb, core/process/exit_spec.rb and core/string/unpack/carret_spec.rb. A count whose population I had not looked at would have published a third wrong number into a change whose whole point is that two were already wrong. ## Checked and NOT a finding, so nobody re-checks it BASELINE's header records that the 2026-11-03 re-record ABSORBED 11 files that went backwards, 8 of them `core/set/*`, -23 examples in all. That reads at first like a transparency gap in a page advertising 23,672. It is not: `layouts/index.html` already discloses the same event as "+144 passing, and 27 examples that went red -- a figure no pass total shows, found by comparing the two runs' failure descriptions". The absorption is that disclosure, not a hidden one. What the published text does not do is LOCALISE it, and the `core/set/*` cluster of 8 is the localisation; that belongs in the ruby repository rather than on this page. `conformancefigure@v0.8.0 --root .` green: 6 total claims, 1 version claim, 3 stubbed-helper mentions against 23,672 at Ruby 4.0.9. Co-Authored-By: Claude Opus 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.
landing: this page states two counts of one thing, and the stale one is undated
hugo.toml:74says 2,202 of 2,206 spec files produce a result, "the other 4recorded as FILEFAIL".
layouts/_default/list.html:78says "10 of 2,206 specfiles produce no result". Same site, same corpus, both in the present tense,
4 against 10.
Derived from the record CI actually enforces --
scripts/conformance/rubyspec/BASELINEon the ruby repository's main -- there are 4 FILEFAIL rows. hugo.toml is
right; list.html carries the 2026-09-26 run's figure, two months old.
⛔ The fix is NOT to change 10 into 4. That whole sentence is one dated run:
"93.3% pass (22,488 of 24,116); 477 more are skipped ... 10 of 2,206 produce no
result". Dropping a November count into a September sentence makes the paragraph
internally inconsistent while every individual number looks defensible -- the
shape where two errors cancel and nothing shows it. So the run is NAMED, the
sentence is left as that run's shape, and the current baseline count is stated
beside it with the reason.
⛔ Counting FILEFAIL needed care, which is worth recording:
grep -c FILEFAIL BASELINEanswers 5, because line 2 is the header comment that EXPLAINS theFILEFAIL format. Reading the matching lines instead of trusting the count gives
4 -- at core/kernel/exit_spec.rb, core/mutex/lock_spec.rb,
core/process/exit_spec.rb and core/string/unpack/carret_spec.rb. A count whose
population I had not looked at would have published a third wrong number into a
change whose whole point is that two were already wrong.
Checked and NOT a finding, so nobody re-checks it
BASELINE's header records that the 2026-11-03 re-record ABSORBED 11 files that
went backwards, 8 of them
core/set/*, -23 examples in all. That reads at firstlike a transparency gap in a page advertising 23,672.
It is not:
layouts/index.htmlalready discloses the same event as "+144passing, and 27 examples that went red -- a figure no pass total shows, found by
comparing the two runs' failure descriptions". The absorption is that disclosure,
not a hidden one. What the published text does not do is LOCALISE it, and the
core/set/*cluster of 8 is the localisation; that belongs in the rubyrepository rather than on this page.
conformancefigure@v0.8.0 --root .green: 6 total claims, 1 version claim, 3stubbed-helper mentions against 23,672 at Ruby 4.0.9.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com