CI failures retriever should exclude stale old Try pushes

Open
#6,544 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
databases, testing-qa

Research direction

Locate the CI failures database retriever and the logic that determines the effective oldest Try push date. Inspect how stale July 2025 Try pushes influence the date range, then verify that they are excluded and that unnecessary autoland pushes are no longer retrieved for ranges without Try pushes.

Written by the indexing model from the issue text.

Description

The CI failures database created by the retriever contains a few stale Try pushes from July 2025. To deterministically retrieve the (effective) oldest Try push date in the database, these should be excluded. This prevents unnecessary processing and retrieving of autoland pushes with CI failures for the range without Try pushes - at the moment July 2025 to April 2026.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 13h
Merged PRs (30d)
65

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/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.