Add JRuby for Windows on Arm #1597
test.yml
on: pull_request
Test .ruby-version
4s
Test .tool-versions
4s
Test mise.toml
7s
Test with no Gemfile
22s
Test with no Gemfile but with bundler-cache
19s
Test rubygems: version upgrades RubyGems to that version if the default is older
25s
Test rubygems: version noops if the default is newer
5s
Test rubygems: version uses the Bundler installed by the rubygems update
9s
Test bundler: 1.x for old Ruby
20s
Test with a major Bundler version
20s
Test with a minor Bundler version
20s
Test with an exact Bundler version
19s
Test with a Bundler pre/rc version
20s
Test BUNDLED WITH Bundler dev
5s
Test gemfile depending on Bundler 1
23s
Test installing a Gemfile with nokogiri on TruffleRuby
19s
Test windows-toolchain: none
21s
lint
14s
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Annotations
4 errors, 4 warnings, and 20 notices
|
ubuntu-22.04-arm jruby-head
The process '/home/runner/.rubies/jruby-head/bin/ruby' failed with exit code 1
|
|
ubuntu-22.04-arm jruby
The process '/home/runner/.rubies/jruby-10.0.2.0/bin/ruby' failed with exit code 1
|
|
ubuntu-24.04-arm jruby-head
The process '/home/runner/.rubies/jruby-head/bin/ruby' failed with exit code 1
|
|
ubuntu-24.04-arm jruby
The process '/home/runner/.rubies/jruby-10.0.2.0/bin/ruby' failed with exit code 1
|
|
windows-2022 2.0
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.1
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.3
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
windows-2022 2.2
Renaming C:\Windows\System32\libcrypto-1_1-x64.dll and C:\Windows\System32\libssl-1_1-x64.dll to avoid dll resolution conflicts on Ruby < 2.4
|
|
Test windows-toolchain: none
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
|
windows-2025 3.4
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 3.3
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 ucrt
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.0
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 mingw
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 mswin
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 3.0
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 3.1
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 3.2
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 ruby-head
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.1
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.4
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.2
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.3
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.7
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.5
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 2.6
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 jruby-head
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|
|
windows-2025 jruby
Windows-2025 runners will change the working directory to a new D:/ drive beginning on 2025-08-18. For more details see https://github.com/actions/runner-images/issues/12744.
|