For performance regressions, delay adding the regressor needinfo after the first needinfo has been cleared
Open
Nobody has claimed this yet.
area-Noise Reduction
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
bugbot shouldn't set needinfo again after it's cleared.
There's no point of setting it again and it's just annoying.
https://bugzilla.mozilla.org/show_bug.cgi?id=1959968#c2
https://bugzilla.mozilla.org/show_bug.cgi?id=1959085#c5
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing the performance-regression handling that adds the regressor needinfo, then compare its behavior with the two linked Bugzilla cases. Done means the bot does not re-add that needinfo after the first one has been cleared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100