ci: test coverage for ruby 3.1 #2408
Merged
Conversation
This file contains 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
flavorjones
force-pushed
the
2397-support-ruby-3-1
branch
from
90699ec
to
92b33ab
Compare
|
This PR is a work-in-progress as rake-compiler-dock has not yet officially shipped Ruby 3.1 support. |
Note that this commit doesn't include building or testing native gem support for Ruby 3.1.
removing ruby_xmalloc from the stack
See #2375 for context Co-authored-by: MSP-Greg <Greg.mpls@gmail.com>
flavorjones
force-pushed
the
2397-support-ruby-3-1
branch
from
eda623a
to
bb9f952
Compare
|
#2409 will complete Ruby 3.1 support, so merging this. |
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.
What problem is this PR intended to solve?
See #2397 which describes supporting Ruby 3.1 in precompiled native gem releases.
Have you included adequate test coverage?
Yes!
Does this change affect the behavior of either the C or the Java implementations?
No behavioral changes.