Separate Analysis and Fix stages in Test Repair Agent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
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
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.
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.
Assessment
- Tech stack
- python
- Domain
- devtools, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100