Skip to content

Conversation

@MSP-Greg
Copy link
Collaborator

No description provided.

@MSP-Greg
Copy link
Collaborator Author

MSP-Greg commented Aug 22, 2022

Something is odd with the Windows 2019 20220814.1 image, as it fails.

But, I had a CI run checking master a few hours earlier using 20220821.1, and it passed.

EDIT: The earlier Windows image has MSYS2 MinGW gcc 12.1.0 installed, but the newer image has gcc 12.2.0, and the builds are done on Windows 2022, which used 12.2.0.

I don't recall seeing or hearing of this type of issue, and it would be a real PITA to fix it.

As you may recall, the Windows 2019 image has mingw build tools installed, Windows 2022 does not. Or, when using Windows 2022, the MSYS2 package archives built in ruby/setup-msys2-gcc are installed. And they're updated three times a day.

So, if you have to use Windows 2019 MinGW, update the build tools. Or, make things simple and just run CI on Windows 2022.

@eregon eregon force-pushed the 00-ruby-loco-bash branch from 2ba4fb1 to ebe74a8 Compare August 23, 2022 16:41
@eregon
Copy link
Member

eregon commented Aug 23, 2022

I changed the check a little bit, should be equivalent.

Those failures are very strange: https://github.com/ruby/setup-ruby/runs/7960716852?check_suite_focus=true
I'll wait CI.

@eregon
Copy link
Member

eregon commented Aug 23, 2022

Ah, it's because it's already failing on master, which rake doesn't work on CRuby 2.5+ :/
https://github.com/ruby/setup-ruby/runs/7938245817?check_suite_focus=true
I'll adapt the test I guess.

@eregon
Copy link
Member

eregon commented Aug 23, 2022

All green now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants