Test this action

Add jruby-10.0.2.0 #1595

Sign in to view logs

Triggered via pull request August 11, 2025 19:04

ruby-builder-bot

opened #795

ruby-builder-bot:jruby-10.0.2.0

Status Failure

Total duration 5m 15s

Artifacts –

test.yml

on: pull_request

Test .ruby-version

Test .tool-versions

Test with no Gemfile

Test with no Gemfile but with bundler-cache

Test rubygems: version upgrades RubyGems to that version if the default is older

Test rubygems: version noops if the default is newer

Test rubygems: version uses the Bundler installed by the rubygems update

Test bundler: 1.x for old Ruby

Test with a major Bundler version

Test with a minor Bundler version

Test with an exact Bundler version

Test with a Bundler pre/rc version

Test BUNDLED WITH Bundler dev

Test gemfile depending on Bundler 1

Test installing a Gemfile with nokogiri on TruffleRuby

Test windows-toolchain: none

Matrix: test

Matrix: testGemfileMatrix

Matrix: testLatestRubygemsVersion

Annotations

1 error, 4 warnings, and 1 notice

Test installing a Gemfile with nokogiri on TruffleRuby

The process '/home/runner/.rubies/truffleruby-head/bin/bundle' 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.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.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

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