-
Notifications
You must be signed in to change notification settings - Fork 43
Fix JRuby CI for Windows #151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@kou I'll get that job running and then merge this. |
|
I mean I'll get it running and then let you merge this. 😀 |
|
@kou Please hold off on release... I may have found one more bug running HexaPDF tests. |
@headius Could you make a PR to setup-ruby to fix that? It would be good to avoid adding many |
|
Mmh, it should work fine since https://github.com/ruby/setup-ruby/blob/eaecf785f6a34567a6d97f686bbb7bccc1ac1e5c/ruby-builder.js#L59 is done on Windows too. I suppose |
|
It seems that rake-compiler uses |
|
Good point. Maybe the mix of / and \ then? In fact in the failed job we do see: clearly that's javac without JAVA_HOME/bin in front. |
|
Ah, |
* See discussion on ruby#151
The setup-ruby logic for JRuby on Windows must not be fully choosing Java 21, so when it tries to compile the extension it's still using an older version. This fixes it.