Refresh our CI configuration

[deivid-rodriguez]

No description provided.

[PragTob]

👋

• thanks + 💚

JRuby failures... I was hoping I could help right now but I gotta run and likely won't be back all day. Might be able to take a look tomorrow. I'll try and trigger a build on the main branch.

     # ./spec/return_codes_spec.rb:10:in `block in <main>'

  2) return codes inside fixtures/frameworks when running testunit_bad.rb behaves like bad tests with default configuration prints a message to STDERR
     Failure/Error: expect(@stderr).to eq "SimpleCov failed with exit #{@status.exitstatus}\n"

       expected: "SimpleCov failed with exit 1\n"
            got: ""

       (compared using ==)

       Diff:
       @@ -1,2 +1 @@
       -SimpleCov failed with exit 1
     Shared Example Group: "bad tests" called from ./spec/return_codes_spec.rb:66
     # ./spec/return_codes_spec.rb:37:in `block in <main>'
     # ./spec/return_codes_spec.rb:12:in `block in <main>'
     # ./spec/return_codes_spec.rb:10:in `block in <main>'

Finished in 2 minutes 1.7 seconds (files took 1.99 seconds to load)
335 examples, 2 failures

Failed examples:

rspec './spec/return_codes_spec.rb[1:1:4:1:1:2]' # return codes inside fixtures/frameworks when running rspec_bad.rb behaves like bad tests with default configuration prints a message to STDERR

[deivid-rodriguez]

I'm confused, since it passes for me locally 😬

[deivid-rodriguez]

The base OS upgrades and switching to the official ruby action in the unstable workflow were messing things up, so I reverted those changes.

[PragTob]

Thanks a ton 💚