Skip to content
Test this action

Use new releases of ruby-builder per engine-version #1622

Sign in to view logs

Use new releases of ruby-builder per engine-version

Use new releases of ruby-builder per engine-version #1622

Triggered via push September 21, 2025 18:52
@eregoneregon
pushed cf7216d
master
Status Success
Total duration 5m 41s
Artifacts –

test.yml

on: push
Test .ruby-version
5s
Test .ruby-version
Test .tool-versions
6s
Test .tool-versions
Test mise.toml
6s
Test mise.toml
Test with no Gemfile
20s
Test with no Gemfile
Test with no Gemfile but with bundler-cache
21s
Test with no Gemfile but with bundler-cache
Test rubygems: version upgrades RubyGems to that version if the default is older
23s
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
8s
Test rubygems: version uses the Bundler installed by the rubygems update
Test bundler: 1.x for old Ruby
21s
Test bundler: 1.x for old Ruby
Test with a major Bundler version
21s
Test with a major Bundler version
Test with a minor Bundler version
22s
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
21s
Test with a Bundler pre/rc version
Test BUNDLED WITH Bundler dev
6s
Test BUNDLED WITH Bundler dev
Test gemfile depending on Bundler 1
27s
Test gemfile depending on Bundler 1
Test windows-toolchain: none
20s
Test windows-toolchain: none
lint
13s
lint
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Fit to window
Zoom out
Zoom in

Annotations

4 warnings and 1 notice
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