MozillaSecurity / MozillaSecurity/bugmon
Don't update bugs when confirmation and bisection conflict
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 2
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 1
Description
In cases where the bug is found to have been fixed during the confirmation stage, but bisection fails because the end build crashes, we should ignore the result and not update the bug.
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 by tracing how confirmation results and bisection results are handled, especially when the end build crashes. Reproduce the conflict described in the issue and verify that a confirmed fix leaves the Bugzilla bug unchanged when bisection fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100