Can't match rspec errors in 9.4.2.0

[jcoyne]

In MRI 3.1, I'm able to run this rspec test where it has an implied error type of RuntimeError, however in jRuby I have to be explicit about the error type or I receive the following error:

     Failure/Error: expect { request }.to raise_error 'Verboten!'

       expected Exception with "Verboten!", got #<TypeError: exception class/object expected> with backtrace:

Similar to #7112

Using rspec 3.12.0

The code for this matcher is here

• https://github.com/rspec/rspec-expectations/blob/main/lib/rspec/matchers.rb#L773
• https://github.com/rspec/rspec-expectations/blob/main/lib/rspec/matchers/built_in/raise_error.rb#L18

[enebo]

I am not seeing this locally but perhaps my attempts at making a repro is wrong OR dependent gems of rspec differ?

def request
  raise RuntimeError.new 'Verboten!'
end

context "A" do
  it "should" do
    expect { request }.to raise_error 'Verboten!'
  end
end

~/releases/9.4.2.0/jruby-9.4.2.0/bin/jruby -S rspec ../snippets/err.rb 
.

Finished in 0.05344 seconds (files took 0.33124 seconds to load)
1 example, 0 failures

rspec (3.12.0)
rspec-core (3.12.2)
rspec-expectations (3.12.3)
rspec-mocks (3.12.5)
rspec-support (3.12.0)

[enebo]

@jcoyne Looking at #7112 it appears that was caused due to an underlying bug with prepend. So I am guessing my repro is not doing something your code is (prepend refinements).

[jcoyne]

Hmm.... for some reason I can't duplicate this on my local machine either 😠 it's only in CI: https://github.com/sul-dlss/searchworks_traject_indexer/actions/runs/4750303631/jobs/8438358385

[enebo]

@jcoyne Is it possible something extra is loaded as part of the CI job? I also tried with --dev and compiled so I don't think that would differ.

[jcoyne]

No, I don't think it's loading any loading differently.