mozilla / mozilla/bugbot

Set the `status-firefox###` flag to `affected` when the Intermittent Failures Robot reports recent failures

Open
#1,657 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Intermittents
Dominant language
Python
Stars
68
Forks
92
Avg merge
2d 2h
Merged PRs (30d)
16

Description

The Intermittent Failures Robot adds "X failures in Y pushes were associated with this bug in the last Z days" bug comments.

Suggestion: to help track affected versions, the Intermittent Failures Robot or autonag could also set the bug's status-firefox### flag to affected (unless the current status is wontfix or fix-optional, indicating that someone knows that version is affected but decided that it doesn't require a fix).

Old status-firefox### value New status-firefox### value
--- affected
? affected
unaffected affected
affected (no change needed: we already know this version is affected)
fix-optional (no change needed: we already knows this version is affected)
fixed affected
wontfix (no change needed: we already knows this version is affected)
verified affected
disabled affected (no change needed: test failure for a feature that is disabled for users)
verified disabled affected (no change needed: test failure for a feature that is disabled for users)

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by locating the Intermittent Failures Robot or autonag code that reports recent failures and updates Bugzilla metadata. Trace how status-firefox### values are read and changed, then add coverage for the listed status transitions and verify that disabled, verified disabled, fix-optional, and wontfix cases remain unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.