Build failures cause unscheduled tasks which cause no results to ever be written to bugs

Open
#422 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
backend

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.

Description

Bug Easy

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.

Dominant language
Python
Stars
9
Forks
8
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla-services/updatebot

All issues in mozilla-services/updatebot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.