From: Greg.mpls@... Date: 2020-12-07T16:10:51+00:00 Subject: [ruby-core:101285] [Ruby master Bug#17372] Actions Windows MinGW failures 2020-12-06 Issue #17372 has been updated by MSP-Greg (Greg L). @Eregon @hsbt The cause of the failure in the MinGW CI is the setting of `ENV['BUNDLER_VERSION']` by ruby/setup-ruby, and also the fact that the RubyGems test suite (maybe TestCase?) is not accounting for that ENV variable in its setup. I removed the setting in both ruby-loco and the MinGW CI here, and all of them passed. As mentioned above, I couldn't repo this locally, and the ruby-loco build passed in AppVeyor. Neither had `ENV['BUNDLER_VERSION']` set... I may do a PR, as this should be guarded against regardless? ---------------------------------------- Bug #17372: Actions Windows MinGW failures 2020-12-06 https://bugs.ruby-lang.org/issues/17372#change-88963 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- JFYI, I'm trying to sort out the recent failures in Windows mingw. ruby-loco Actions builds (both mingw & mswin) are failing, same tests failing as mingw CI here. ruby-loco AppVeyor build (only mingw) is passing. Both ruby-loco mingw builds (Actions & AppVeyor) use the same scripts. Can't repo the failures locally. Frustrated... -- https://bugs.ruby-lang.org/ Unsubscribe: