-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
Windows JRuby - recent failure #339
Comments
What's the value of IO::NULL on JRuby on Windows? Maybe it's not the correct one? I've noticed it as well, and it's quite weird it started failing. |
i.e., failure on this action's CI: https://github.com/ruby/setup-ruby/runs/6450274289?check_suite_focus=true |
This looks relevant: jruby/jruby#7182 |
Sorry, I should have posted some links. Given that logs are removed, I sometimes just grab the pertinent log output. This is odd. But, I've also noticed an issue that is similar to using Windows mingw and ucrt files, which can have very strange problems.. Re the juby issue above, that's 20 days old, but CI passed just six days ago here - https://github.com/ruby/setup-ruby/runs/6374617633. That was with a cache, but it logged things before the cache restore that aren't logged in the recent failures. Confused, with very little Java/JRuby knowledge... EDIT: See jruby/jruby#7217 |
actions/runner-images#5524 happened 6 days ago Java changed from |
This should be fixed in the July JDK release, so let's just wait for that (ruby-git/ruby-git#582). |
Is this error the same or something new? Error: Error: Unexpected HTTP response: 404
[27](https://github.com/halostatue/minitar/runs/7188010152?check_suite_focus=true#step:3:34)
at D:\a\_actions\ruby\setup-ruby\v1\dist\index.js:7561:25
[28](https://github.com/halostatue/minitar/runs/7188010152?check_suite_focus=true#step:3:35)
at Generator.next (<anonymous>)
[29](https://github.com/halostatue/minitar/runs/7188010152?check_suite_focus=true#step:3:36)
at fulfilled (D:\a\_actions\ruby\setup-ruby\v1\dist\index.js:7471:58)
[30](https://github.com/halostatue/minitar/runs/7188010152?check_suite_focus=true#step:3:37)
at runMicrotasks (<anonymous>)
[31](https://github.com/halostatue/minitar/runs/7188010152?check_suite_focus=true#step:3:38)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Run tests |
FWIW, the latest jruby-head on Windows is completely broken currently: jruby/jruby#7106 |
ruby/setup-ruby#339 https://bugs.openjdk.org/browse/JDK-8285445 Can be removed once the July 2022 JDK release is available.
ruby/setup-ruby#339 https://bugs.openjdk.org/browse/JDK-8285445 Can be removed once the July 2022 JDK release is available. (cherry picked from commit 5d53b59)
Workaround for the issue reported in ruby/setup-ruby#339
It should be possible to build a JRuby bundle for Windows without using Windows, but I suppose setup-ruby does not work that way. jruby/jruby#7106 will be fixed soon, but I'm unclear why it started to fail. |
GitHub Actions updated the JDK, which fixes the jruby/jruby#7106 being fixed means jruby-head on Windows is also fixed now. |
Recent CI using Windows and both jruby and jruby-head are failing.
Running
bundle env
in my fork showsThe Ruby code line (
lib/ruby/stdlib/rubygems/resolver.rb:176
) is:@headius any ideas? Of course, running
bundle env
locally works fine...The text was updated successfully, but these errors were encountered: