Use only Windows Server 2019 runners for CI in GitHub Actions #4883
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
gem install ronn
step in our Windows CI workflow currently fails on newer Windows Server 2022 GitHub Actions runners, due to possibly some missing C headers or libraries. The error looks like:Ideally we would continue to use the
windows-latest
runners and adjust the step which runs the now-deprecatedactions/setup-ruby@v1
action so that it runsruby/setup-ruby@v1
instead, as recommended.However, doing so introduces a set of problems whereby a different Bash shell is used and our
PATH
environment variable settings are not respected, the result being that when our tests rungit lfs
the system default Git LFS binary is found by Git and executed instead of the newly-builtgit-lfs.exe
which we want to test, leading to many test failures.So, for the time being, we resort to fixing our Windows CI and release runners to use Windows Server 2019, until the problems can be sorted out upstream.
Also, because the
.github/workflows/ci.yml
file only needs to be readable, not executable, we revise its file permissions./cc actions/runner-images#5100
/cc ruby/setup-ruby#293