Implement some back-off strategy for Intermittent bug closing.

Open
#2,589 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by locating the intermittent bug closing and reopen-notification logic in the bugbot codebase, then trace how each reopen determines the next closing interval. Clarify whether linear or exponential backoff is intended and verify that repeated reopens produce fewer notification events while the existing closing behavior remains intact.

Written by the indexing model from the issue text.

Description

area-Intermittents

Due to the 3 (or 2) week intermittent bug closing behavior, I'm getting 20-30 mails per week for closing intermittent bugs and 20-30 mails per week for reopening these bugs from the 10 bugzilla components I'm subscribed to.

This is annoying and creates a lot of noise.

Please implement either exponential or linear backoff strategy to reduce the noise of these mails. (time x2 per reopen or time +2 / +3 weeks per reopen).

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

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.

More from mozilla/bugbot

All issues in mozilla/bugbot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.