Open MSP-Greg opened 4 years ago
https://github.com/MSP-Greg/actions-windows-info-ruby/runs/435335620?check_suite_focus=true looks nice.
It would be interesting how values change after ruby/setup-ruby
, could you schedule a run with that?
I could run where.ps1
in https://github.com/ruby/setup-ruby/blob/master/.github/workflows/test.yml if that's helpful.
Next I'm going to see if I can get spec & test-all to work with the native encoding (UTF-8) in Actions. Both work with the native encoding that AppVeyor uses (IBM437).
Yes, I think it's a bug specs don't pass with UTF-8 on Windows. PRs to ruby/spec welcome :)
@eregon
could you schedule a run with that?
See: https://github.com/MSP-Greg/actions-windows-info-ruby/runs/436325107
I also added ruby.exe
and sed.exe
to where.ps1
Re the tests and UTF-8, I've got a few things to change in MSP-Greg/actions-ruby and MSP-Greg/ruby-loco first.
You could even add ruby-loco's mingw & mswin builds to ruby/spec...
@eregon
Thought I'd collect as many of the "how's this set up?" code snippets and put them in one repo.
In the Actions runs, the last step is 'where & version info', which shows info about various exe & dll files that are in PATH (on Windows, 'where' is the equivalent of 'which').
Since I work with CI in several gems that compile with OpenSSL, that was the reason for my removing many of the locations from PATH. I think I'll do some of that in actions-ruby if the OpenSSL package is installed. I'm revising it quite a bit, along with the mswin addition to the ruby-loco release...
Off-topic:
Next I'm going to see if I can get spec & test-all to work with the native encoding (UTF-8) in Actions. Both work with the native encoding that AppVeyor uses (IBM437).