MSP-Greg

Messy issue. All the affected Rubies are EOL. Also, they report `ASCII-8BIT` to the following, but Ruby 3.0 and later report `UTF-8`: ``` ruby -e "puts ENV['PATH'].encoding" ``` See https://github.com/ruby/ruby/pull/3818...

@junaruga JFYI, the MSYS2 script (and the config section) is here: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-openssl/PKGBUILD#L88 MSYS2 is used for all the standard publicly available Windows Rubies. One can also build Rubies with MSFT...

Jon, I wanted to create an issue in case something else causes the same error. Sometime I'll investigate more, but I've got a few other 'fires' that need attending...

I just ran the same tests on Appveyor, and I got the same error. I briefly looked at the code: https://github.com/rspec/rspec-core/blob/77dbc84657c5dc45e07a7fe0f5b02b4caeb6c9ad/lib/rspec/core/backtrace_formatter.rb#L8-L20 I may try and adjust the code and see...

I haven't thought about possible solutions, but this may be due to how Azure Pipelines deals with ANSI escape sequences, which don't affect the displayed logs... Ok to close.

You're testing on Appveyor (maybe add 2.6 or trunk?), so you're doing fine. I wonder if [`String#scrub`](https://msp-greg.github.io/ruby_trunk/Core/String.html#scrub-instance_method) would help here? Never used it. Maybe something involving a `str[/\e/]` check?

Bundler has some color 'add-ins' that are used in their testing, and the issue is only ocurring when bundler is tested as it exists in the ruby/ruby repo. I'm assuming...

That would be a big breaking change. Other people have asked for mswin release builds. I'm wondering if it's time to have release builds, maybe starting with Ruby 3.2, as...

@jmarrec Never tried. Let me see what I can do locally. Might I ask why you'd like a build like this? Anything to do with SketchUp (since it uses Ruby)?

Re the workflow you linked to, have you thought about running an MSY2 head build (`head` or `ucrt`)? Or, wondering if the failure is mswin specfic...