reports: limit regzbot tags and lore link to upstream trees#1987
Open
bhcopeland wants to merge 2 commits into
Open
reports: limit regzbot tags and lore link to upstream trees#1987bhcopeland wants to merge 2 commits into
bhcopeland wants to merge 2 commits into
Conversation
alanpeixinho
approved these changes
Jul 13, 2026
alanpeixinho
left a comment
alanpeixinho
left a comment
Contributor
There was a problem hiding this comment.
Tested for different issues from different trees, seems ok.
Member
Author
|
@alanpeixinho I thought it would make sense to put stable in here. I've added it as an additional commit, since it isn't much to add. |
tales-aparecida
approved these changes
Jul 14, 2026
| KERNELCI_REPLYTO = "kernelci@lists.linux.dev" | ||
| REGRESSIONS_LIST = "regressions@lists.linux.dev" | ||
|
|
||
| REGZBOT_TREES = ("mainline", "next", "stable") |
There was a problem hiding this comment.
nit https://docs.astral.sh/ruff/rules/literal-membership/
Suggested change
| REGZBOT_TREES = ("mainline", "next", "stable") | |
| REGZBOT_TREES = {"mainline", "next", "stable"} |
Member
Author
There was a problem hiding this comment.
Thanks! Amended and squashed; appreciated.
@alanpeixinho if you don't trust the test suite, please update it 🙏🏼 |
Regression reports currently carry the #regzbot tags and a lore link to their own Message-ID regardless of the tree, but only mainline and next reports are CC'd to the regressions list. Reports for other trees (android, chromeos and so on) are out of regzbot's scope, and their lore link can point at a mail that never reached lore. Gate the regzbot tags and the lore link on the same tree check that adds the regressions list CC, through a shared is_regzbot_tree() helper, so the tags only appear on reports that regzbot will actually see and the link only appears on mails guaranteed to be archived. Reports for other trees keep the Reported-by attribution and the Signed-off-by: Ben Copeland <ben.copeland@linaro.org>
Regzbot also tracks regressions in proper stable releases, so add the stable tree to the set whose reports carry the regzbot tags, the lore link and the regressions list CC. Signed-off-by: Ben Copeland <ben.copeland@linaro.org>
bhcopeland
force-pushed
the
regzbot-upstream-gating
branch
from
b49f047 to
9c32a47
Compare
tales-aparecida
approved these changes
Jul 14, 2026
mentonin
approved these changes
Jul 14, 2026
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
4 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.
Regression reports currently carry the #regzbot tags and a lore link to their own Message-ID regardless of the tree, but only mainline and next reports are CC'd to the regressions list. Reports for other trees (android, chromeos and so on) are out of regzbot's scope, and their lore link can point at a mail that never reached lore.
Gate the regzbot tags and the lore link on the same tree check that adds the regressions list CC, through a shared is_regzbot_tree() helper, so the tags only appear on reports that regzbot will actually see and the link only appears on mails guaranteed to be archived. Reports for other trees keep the Reported-by attribution and the