Skip to content

Add JRuby for Windows on Arm #1602

Add JRuby for Windows on Arm

Add JRuby for Windows on Arm #1602

Triggered via pull request August 20, 2025 08:15
Status Success
Total duration 5m 59s
Artifacts

test.yml

on: pull_request
Test .ruby-version
5s
Test .ruby-version
Test .tool-versions
7s
Test .tool-versions
Test mise.toml
8s
Test mise.toml
Test with no Gemfile
19s
Test with no Gemfile
Test with no Gemfile but with bundler-cache
22s
Test with no Gemfile but with bundler-cache
Test rubygems: version upgrades RubyGems to that version if the default is older
22s
Test rubygems: version upgrades RubyGems to that version if the default is older
Test rubygems: version noops if the default is newer
6s
Test rubygems: version noops if the default is newer
Test rubygems: version uses the Bundler installed by the rubygems update
11s
Test rubygems: version uses the Bundler installed by the rubygems update
Test bundler: 1.x for old Ruby
19s
Test bundler: 1.x for old Ruby
Test with a major Bundler version
22s
Test with a major Bundler version
Test with a minor Bundler version
19s
Test with a minor Bundler version
Test with an exact Bundler version
21s
Test with an exact Bundler version
Test with a Bundler pre/rc version
23s
Test with a Bundler pre/rc version
Test BUNDLED WITH Bundler dev
8s
Test BUNDLED WITH Bundler dev
Test gemfile depending on Bundler 1
24s
Test gemfile depending on Bundler 1
Test installing a Gemfile with nokogiri on TruffleRuby
15s
Test installing a Gemfile with nokogiri on TruffleRuby
Test windows-toolchain: none
24s
Test windows-toolchain: none
lint
11s
lint
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 20 notices
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.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
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
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 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 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 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.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 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 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 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 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 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 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.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.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.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 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 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.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 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 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.