Repository navigation
docs: what the unswept 42% of ruby/spec holds, and cmd/specroll - #917
Merged
Merged
Conversation
The README has always said `library/`, `optional/`, `command_line/` and
`security/` are "not run at all" and that the figure is therefore not a
percentage of Ruby. True, and it left the reader with no idea whether the
unmeasured half was a rounding error or the bulk of the work.
It has now been measured once, against MRI 4.0.7 through the same shim:
970 files differ, MRI passes 3,676 examples in them and rbgo 1,335, and
152 files produce no result on rbgo. Three readings matter more than the
total, and all three change what someone would do next:
- 78 of the unswept files CANNOT be measured under this shim at all.
Every `command_line/` file is built on `ruby_exe`, and `optional/capi`
needs a compiled C extension: MRI itself scores 0 in them. That part
is harness work, not interpreter work.
- The largest single debt is a HANG, not a missing feature: Net::FTP is
442 examples behind and 39 of its 56 files are killed by the clock on
rbgo and none on MRI (#916).
- The rest is concentrated in eight modules, and the outright absences
(Coverage 53, StringScanner's byte methods 27, CGI escapes 19,
WeakRef 9) are small beside them.
Marked as one dated run and NOT a gate, in the same words the table above
it uses: nothing re-measures it, so it is a map of where the work is and
not a figure to quote.
The conformance README gains the two things #915 and #914 added and
nothing documented:
- `KILLED on timeout` and why it is reported BEFORE `DID NOT RUN` --
with the note that reports written before that commit cannot tell a
hang from an absence, and that the timeout should be picked for the
question (60x the file's work to detect a regression; a SHORT budget
to tell a hang from a gap -- net-ftp at 300s was still running after
77 minutes, at 20s it answered in 13).
- `cmd/specroll`, its reconciliation against each report's own footer,
and why the invariant differs between a full and a -quiet report.
- `printable()`: a report holding a spec's raw binary was called "RAGE
Package Format (RPF)" by `file`, and grep then skipped it silently.
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.
The README has always said that
library/,optional/,command_line/andsecurity/are "not run at all", and that the figure is therefore not a percentage of Ruby. True — and it left the reader with no idea whether the unmeasured half was a rounding error or the bulk of the work.It has now been measured once, against MRI 4.0.7 through the same shim.
Three readings matter more than the total, and each one changes what somebody would do next:
command_line/file is built onruby_exe, andoptional/capineeds a compiled C extension: MRI itself scores 0 in them. That part is harness work, not interpreter work — and nothing said so before.Net::FTPis 442 examples behind, and 39 of its 56 spec files are killed by the clock on rbgo and none on MRI (#916).Coverage53,StringScanner's byte methods 27,CGIescapes 19,WeakRef9) are small beside them.It is marked as one dated run and not a gate, in the same words the table above it already uses: nothing re-measures it, so it is a map of where the work is rather than a figure to quote. The gated
language/+core/number is untouched, and all four README gates still pass.The conformance README gains what #914 and #915 added
KILLED on timeout, and why it is reported beforeDID NOT RUN. A killed engine prints noRBGO_RESULTline either, so the absence arms would otherwise claim every killed row — publishing a file the clock stopped as one the engine could not load. With the note that reports written before that commit cannot tell the two apart.net-ftpat 300 s was still running after 77 minutes with nothing printed; at 20 s it answered in 13.cmd/specroll, its reconciliation against each report's own footer, and why the invariant differs between a full and a-quietreport.printable(): a report holding a spec's raw binary was called "RAGE Package Format (RPF)" byfile, and grep then skipped it silently — which is how three checks of one report were passed on nothing.Refs #916 — it stays open; this only stops the README leaving the unswept half
unquantified, and stops those 75 files being described as unimplemented.
🤖 Generated with Claude Code