ci: fix capturing fatal errors in clang problem matcher#51651
Merged
Conversation
dsanders11
added
semver/none
target/40-x-y
nikwen
approved these changes
May 19, 2026
jkleinsc
approved these changes
May 19, 2026
|
No Release Notes |
This was referenced May 19, 2026
Contributor
|
I have automatically backported this PR to "43-x-y", please check out #51710 |
Contributor
|
I have automatically backported this PR to "42-x-y", please check out #51711 |
Contributor
|
I have automatically backported this PR to "40-x-y", please check out #51712 |
Contributor
|
I have automatically backported this PR to "41-x-y", please check out #51713 |
trop
Bot
added
in-flight/42-x-y
in-flight/40-x-y
in-flight/41-x-y
merged/43-x-y
trop
Bot
added
merged/40-x-y
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
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.
Description of Change
Follow-up to #50984. That approach was incomplete because the value captured by the 4th capture group is what GitHub uses as the annotation level, and "fatal error" was being captured and not recognized by GitHub. So swap things around a bit so that only "error" is captured as the level.
Checklist
Release Notes
Notes: none