feat: upgrade to node 24 #1612
Triggered via pull request
September 16, 2025 17:59
chenrui333
Status
Failure
Total duration
6m 34s
Artifacts
–
test.yml
on: pull_request
Test .ruby-version
6s
Test .tool-versions
5s
Test mise.toml
7s
Test with no Gemfile
20s
Test with no Gemfile but with bundler-cache
19s
Test rubygems: version upgrades RubyGems to that version if the default is older
24s
Test rubygems: version noops if the default is newer
5s
Test rubygems: version uses the Bundler installed by the rubygems update
10s
Test bundler: 1.x for old Ruby
19s
Test with a major Bundler version
20s
Test with a minor Bundler version
21s
Test with an exact Bundler version
21s
Test with a Bundler pre/rc version
20s
Test BUNDLED WITH Bundler dev
6s
Test gemfile depending on Bundler 1
24s
Test windows-toolchain: none
19s
lint
3s
Matrix: test
Matrix: testGemfileMatrix
Matrix: testLatestRubygemsVersion
Annotations
1 error, 4 warnings, and 1 notice
|
lint
Process completed with exit code 1.
|
|
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.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
|
|
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
|