Migrate regressions into jruby:spec or remove if already covered#7757
Merged
enebo merged 15 commits intojruby:masterfrom Apr 20, 2023
Merged
Migrate regressions into jruby:spec or remove if already covered#7757enebo merged 15 commits intojruby:masterfrom
enebo merged 15 commits intojruby:masterfrom
Conversation
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
1 participant
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.
Just janitorial. Planning on trying to reduce/eliminate jruby:regression and potentially just have jruby:spec which should cover things we tend to regress and things where we are behaviorally different than Ruby. The overlap on those two is large enough I think this should just be done thing.