Bugs with regressions shouldn't get reported if the patches were backed out
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
For example, https://bugzilla.mozilla.org/show_bug.cgi?id=1542415 showed up on today's "Bugs with more than 3 regressions reported in the last 7 days for the 2019-04-24" But the patch causing the regressions was backed out 2 days ago.
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
Start with the report that produced the 2019-04-24 "more than 3 regressions" result and compare it with Bugzilla bug 1542415. Trace how the report identifies regressions and how it can recognize that the causing patch was backed out. Done means backed-out patches no longer cause these bugs to be reported, while valid regressions still appear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100