mozilla-services / mozilla-services/updatebot
Build failures cause unscheduled tasks which cause no results to ever be written to bugs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
See https://bugzilla.mozilla.org/show_bug.cgi?id=2052735 for an example.
A build failure in https://treeherder.mozilla.org/jobs?repo=try&resultStatus=unscheduled%2Csuperseded%2Ctestfailed%2Cbusted%2Cexception%2Csuccess%2Cretry%2Cusercancel%2Crunning%2Cpending%2Crunnable&revision=c08e22c0574f left many jobs in an unscheduled state (e.g. test-macosx1470-64/opt-gtest-1proc). Eventually they expired, but that takes 28 days.
Contributor guide
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 Bugzilla example and the linked Treeherder revision to trace how build failures and unscheduled jobs are handled. Identify the updatebot entry point responsible for recording results in bugs; done means expired or unscheduled jobs no longer leave the affected bugs without results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100