@MSP-Greg 2.6, 2.7 and 3.0 are failing on Windows, see https://github.com/ruby/setup-ruby/actions/runs/14762192617/job/41445391659
Anything we can/should do about that here?
It looks like it's using the latest gcc which has this known incompatibility.

But this passed (after the failure you mentioned)?
https://github.com/ruby/setup-ruby/actions/runs/14762461010

Confused, am I missing something?

@eregon

Found it.

Run 1505 ran on Image version 20250420.1.0 - passed
Run 1504 ran on Image version 20250427.1.0 - failed

So, the newer image version failed...

@eregon

I hate this sometimes.

"The Windows 2019 Actions runner image will begin deprecation on 2025-06-01 and will be fully unsupported by 2025-06-30"

See actions/runner-images#12045

So, the newer image version failed...

Any idea why the newer image would cause that failure? They updated gcc in the newer image and we use the gcc from the image on windows-2019?