patchwork: derive check context field from CI job name#33
Merged
Conversation
theihor
force-pushed
the
check-context-slug
branch
from
181066f to
da33cb6
Compare
Currently for BPF CI the "context" field of a checks is effectively a
constant with enumerator, for example:
bpf/vmtest-bpf-next-VM_Test-48
This has an undesirable side-effect: different checks (such as "AI
review" vs "test_progs") may overwrite each other, depending on when
they run: for every PR update or for every new revision of the series.
Change how the context identifier is constructed: slugify the job
name, so that the check is associated with a job, independent of the
order or run time.
Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
theihor
force-pushed
the
check-context-slug
branch
from
8736d1c to
196ba44
Compare
danielocfb
approved these changes
Dec 16, 2025
danielocfb
left a comment
danielocfb
left a comment
There was a problem hiding this comment.
Not very familiar with these code paths, but patch seems fine to me; thanks.
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.
Currently for BPF CI the "context" field of a checks is effectively a constant with enumerator, for example:
This has an undesirable side-effect: different checks (such as "AI review" vs "test_progs") may overwrite each other, depending on when they run: for every PR update or for every new revision of the series.
Change how the context identifier is constructed: slugify the job name, so that the check is associated with a job, independent of the order or run time.