Fix jruby CI #3608
Merged
Fix jruby CI #3608
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
The current version constraint is too specific and doesn't allow 10.0.1.0 which was recently released
Collaborator
Author
|
Well, the tests run now but they look proper broken. Much stuff about missing constants. No idea what to do about that. Let me see if going back to 10.0.0.0 solves it |
Collaborator
Author
|
I pinned to 10.0.0.0 for now and opened an upstream issue at jruby/jruby#8923 |
st0012
approved these changes
Jul 22, 2025
Member
st0012
left a comment
st0012
left a comment
There was a problem hiding this comment.
Yeah it looks like something (constant autoloading?) is off on the JRuby side. I think this is a fair mitigation while waiting for JRuby team's response.
tenderlove
approved these changes
Jul 22, 2025
Collaborator
Author
|
I tracked it down to autoloading with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 current version constraint is too specific and doesn't allow 10.0.1.0 which was recently released