Workaround for #446 after windows-2022 runner image updates
#462
Conversation
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
GITHUB_PATH updated so PATH points to that version in following steps. Another workaround for problems with GCC 14/GDB 16 after GitHub windows-2020 runner image was updated to use them. This only buys more time and doesn't fix the underlying problem. Signed-off-by: Jens Reinecke <jens.reinecke@arm.com>
jreineckearm
force-pushed
the
get-tests-going-again
branch
from
03aa88c to
d96904e
Compare
mingw 12.2.0 (GDB 12.1.0 / GCC 12.2.0) to mingw 11.2.0.07112021 (TO BE CONFIRMED) GDB 12.1.0 already shows problems with unicode tests: "can't get string table" error Signed-off-by: Jens Reinecke <jens.reinecke@arm.com>
jreineckearm
force-pushed
the
get-tests-going-again
branch
from
8fa2134 to
3663573
Compare
doesn't help anymore. Signed-off-by: Jens Reinecke <jens.reinecke@arm.com>
jreineckearm
changed the title
windows-2022 runner image updates
|
Added @jonahgraham and @cwalther for awareness. @omarArm , can you please review? |
jonahgraham
approved these changes
Oct 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This PR gets CI going again after a GitHub
windows-2022runner image update that upgrade GNU tools, including an update from GDB 11.2 to 16.2. This resurfaced issues from #446 which had been suppressed for the time being by pinning runner towindows-2022.It introduces the following changes:
windows-latest. Pinning no longer helps with the workaround.windows-2022before (11.2).GITHUB_PATH. Which ensures it's present onPATHfor following steps of that job.Downgrading to GDB 10.2 for Windows testing isn't great. But quickest way to get CI going again.
Picking up #446 next as it's root causes become more and more a problem for our CI on Windows.