mozilla / relman-auto-nag / #6009

24%

master: 26%

push

coveralls-python

Raise the frontend-triage trigger cap to 5 per run so a burst of filings drains in fewer hours

`max_triggers` is a per-run cap and the rule runs hourly, so this raises the ceiling from
72 to 120 runs a day against staff-filed demand of roughly 2.24/day across the nine
components now in scope. Steady state is unaffected -- the cap has never bound at that
rate. What changes is how fast a burst clears: ten bugs from one QA session drained over
four hourly runs at 3 and clears in two at 5, and each run held back was reported in the
email as `left_for_next_run` rather than lost.

The cost is the other thing this cap bounds. It is also the limit on how many unreviewed
Bugzilla comments a bad prompt or ruleset change can produce in one hour before anyone
notices, so that worst case goes from 3 to 5.

No test change: both cap tests set `max_triggers` explicitly rather than reading the
config, and 27 pass.

553 of 3200 branches covered (17.28%)

2370 of 9805 relevant lines covered (24.17%)

0.24 hits per line