Repository navigation
Raise ruby/spec floor 20625 -> 21740 after waves 25 and 26 - #627
Merged
Merged
Conversation
Seven units since the last bump: #617 core/process: spawn, exec, the rlimits, priorities, process groups, kill, the wait family (pass 20 -> 165) #618 core/kernel + core/string: require_relative with an absolute path, the require/load argument contract, LoadError#path, byteindex/ byterindex, split, chop/chars/each_char (kernel 233 -> 184, string 179 -> 153 failing) #620 language: compound assignment evaluation order, the flip-flop operator, magic-comment encodings, loop break values (pass 1308 -> 1443) #622 object: Float#to_s laid out by MRI's rule rather than Go's %g (+11) #624 the mspec shim: a nested describe can see the helpers of the one around it (+28) #625 deps: parser v0.2.0 (language +333) #626 compiler: for-loop targets, block-local variables, what defined? declares (language +382) Measured with scripts/conformance/rubyspec/run.sh against the pinned corpus at 87b1631, 16-way, TIMEOUT=25, three consecutive runs: 21749, 21750, 21750. The floor is set nine below the lowest, the same margin rule as the last bump: it absorbs the run-to-run jitter without being wide enough to hide the loss of a whole spec file, which is what the ratchet exists to catch. #615 (an intermittent frame-pop crash) is still open and can cost a file when it fires. TWO OF THESE ARE NOT VM CONFORMANCE, and the number should not be read as if they were. #624 fixed our own mspec shim: core/string/valid_encoding/utf_8_spec scored 0/28 under MRI 4.0.5 too, so those 28 were harness noise counted as VM failure. #625 is a dependency bump; the VM did not change, but thirteen language spec files became parseable for the first time and brought 333 already- passing examples into view. Both are real gains in what the measurement can see, not in what the VM can do. 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.
Seven units since the last bump.
core/process— spawn, exec, rlimits, priorities, process groups, kill, the wait familycore/kernel+core/string—require_relativewith an absolute path, the require/load argument contract,LoadError#path,byteindex/byterindex,split,chop/chars/each_charlanguage— compound-assignment evaluation order, the flip-flop operator, magic-comment encodings, loopbreakvaluesobject—Float#to_slaid out by MRI's rule rather than Go's%gdescribecan see the helpers of the one around itdefined?declaresMeasurement
scripts/conformance/rubyspec/run.shagainst the pinned corpus at87b1631, 16-way,TIMEOUT=25, three consecutive runs:The floor is set nine below the lowest run, the same margin rule as last time: enough to absorb the run-to-run jitter, not enough to hide the loss of a whole spec file — which is what the ratchet exists to catch. #615, an intermittent frame-pop crash, is still open and can cost a file when it fires.
Two of these are not VM conformance
The number should not be read as if they were.
#624 fixed our own mspec shim.
core/string/valid_encoding/utf_8_spec.rbscored 0/28 under MRI 4.0.5 as well, run through the same shim — those 28 examples were harness noise being counted as VM failure.#625 is a dependency bump. The VM did not change; thirteen
languagespec files became parseable for the first time and brought 333 already-passing examples into view. They were never failing — they were invisible, contributing to neither column.Both are real gains in what the measurement can see, not in what the VM can do. The other five are conformance work.
🤖 Generated with Claude Code