CI(OSGeo4W): Upgrade image to windows-2022 (backport of #5562)#5902
Merged
echoix merged 2 commits intoOSGeo:releasebranch_8_4from Jun 17, 2025
Merged
CI(OSGeo4W): Upgrade image to windows-2022 (backport of #5562)#5902echoix merged 2 commits intoOSGeo:releasebranch_8_4from
echoix merged 2 commits intoOSGeo:releasebranch_8_4from
Conversation
The windows-2019 image is being removed in less than a month. We need to use windows-2022. The changes needed in our build_osgeo4w.sh script relate to the msys2 paths added to path. They need to use the location defined in the CI step, otherwise, another version already installed in the runner, but normally not on path, is used. On windows-2019, we didn’t see errors of this misconfiguration, but we did for windows-2022. * CI(OSGeo4W): Upgrade image to windows-2022 * mswindows: Update path for dumpbin in mklibs.sh * windows: Use MSYS2_LOCATION env var to create script from templates in build_osgeo4w.sh * CI(OSGeo4W): Add MSYS2_LOCATION env var to build stage
github-actions
bot
added
windows
Member
Author
|
Top many failed tests. Need to check out what's missing |
The windows-2019 image is being removed in less than a month. We need to use windows-2022. The changes needed in our build_osgeo4w.sh script relate to the msys2 paths added to path. They need to use the location defined in the CI step, otherwise, another version already installed in the runner, but normally not on path, is used. On windows-2019, we didn’t see errors of this misconfiguration, but we did for windows-2022. * CI(OSGeo4W): Upgrade image to windows-2022 * mswindows: Update path for dumpbin in mklibs.sh * windows: Use MSYS2_LOCATION env var to create script from templates in build_osgeo4w.sh * CI(OSGeo4W): Add MSYS2_LOCATION env var to build stage
Member
Author
|
16 minutes to run the r.univar test... but it made it. I don't expect this run to have enough passing tests. |
Member
Author
81% of the files passed, it is like before for releasebranch_8_4. |
Member
Author
|
It was needed. It failed in the same way after the same amount of time. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Backport of #5562
The windows-2019 image is being removed in less than a month. We need to use windows-2022. The changes needed in our build_osgeo4w.sh script relate to the msys2 paths added to path. They need to use the location defined in the CI step, otherwise, another version already installed in the runner, but normally not on path, is used. On windows-2019, we didn’t see errors of this misconfiguration, but we did for windows-2022.
CI(OSGeo4W): Upgrade image to windows-2022
mswindows: Update path for dumpbin in mklibs.sh
windows: Use MSYS2_LOCATION env var to create script from templates in build_osgeo4w.sh
CI(OSGeo4W): Add MSYS2_LOCATION env var to build stage