mozilla / relman-auto-nag / #6063

24%

master: 26%

Build Type

push

coveralls-python

Committed by DonalMe

Commit Message

Post the REO release regression status to Slack

Ported from mozilla/releases_insights, where this ran as a GitHub Action over
anonymous Bugzilla queries. That is the reason for the move: an anonymous
search never returns a restricted bug, so every count it posted silently
excluded them. Running as bugbot, the same queries see them.

Two rules under bugbot/rules, one per message, over the queries and formatting
they share in bugbot/reo_regressions.py:

- the cycle summary, `reo_regression_slack`, posted Mon and Thu, splitting
  each channel's open regressions into new and carry over
- the action required message, `reo_regression_slack_daily`, ungated and so
  posted every weekday, listing only the regressions stuck long enough to need
  a nudge, plus the fixes nobody has asked to uplift

The summary decides its two days in the rule rather than in configs/rules.json,
as `missed_uplifts` and `workflow.p2_merge_day` decide theirs: the cadence is
part of what that message is -- it reports how a cycle is going rather than
what has just changed, and says so in its own wording -- so a day added to it
in configuration would not make the message any more true.

Restricted bugs are counted and linked like any other but never named: no
message prints a bug summary, which is the line `BzCleaner.get_summary` draws.
The top-level bullet says how many of its count are restricted, because a
reader without access opens the link and finds a shorter list than the number
they clicked on.

One query change worth calling out: `burndown_query` narrows "still marked
affected" to the fixes worth chasing, and being in a security group is one of
the three ways in. Under anonymous queries that branch matched nothing, so the
burndown lines grow here beyond the general restricted-bug increase.

Neither rule is a BzCleaner. They run several queries rather than one, report
counts rather than a table of bugs, write nothing to Bugzilla, and have to
post on a quiet day to say so -- whe... (continued)

Coverage Stats

603 of 3288 branches covered (18.34%)

199 of 302 new or added lines in 3 files covered. (65.89%)

3 existing lines in 1 file now uncovered.

2608 of 10143 relevant lines covered (25.71%)

0.26 hits per line