Separate Analysis and Fix stages in Test Repair Agent
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by reading the related issues #6662 and #6667, then trace the Test Repair Agent workflow and the platform's support for multi-stage workflows. Define separate analysis and fix stages, with the fix independently verifiable through a build or equivalent check, and confirm that analysis can be delivered without waiting for the fix.
Written by the indexing model from the issue text.
Description
Sheriffs care only about the analysis. The fix is for developers. This can help reduce latency; see #6662. We don't run the build for the fix now to reduce runtime, so this would allow us to speed up the delivery of the analysis and verify the fix properly. It likely depends on the ability of the platform to support multi-stage workflows. See #6667
- 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 ·