CI failures retriever should exclude stale old Try pushes
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 6h
- Merged PRs (30d)
- 71
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.
More from mozilla/bugbug
-
good-first-bug hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
good-first-bug hackbot
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
hackbot
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·