Feature: Implement parallel test execution for mono-repos - #248
Open
pradeep0153 wants to merge 1 commit into
Open
Feature: Implement parallel test execution for mono-repos#248pradeep0153 wants to merge 1 commit into
pradeep0153 wants to merge 1 commit into
Conversation
|
@pradeep0153 is attempting to deploy a commit to the sreerevanth's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #247.
Description
This PR executes a major architectural enhancement to support complex mono-repo setups. Repopilot currently relies on a single
sandbox.run_tests()execution blocking the main agent loop.When working with large mono-repos (e.g., a project with a Python backend and a React frontend), modifying a shared type definition or API schema might require running both
pytest(backend) andvitest(frontend) to guarantee that the modification didn't break contracts on either side of the stack. Becausesandbox.pyonly accepts a singlerunner, the agent was mathematically blind to failures in the secondary test suite until a human caught it in CI. We needed to implement concurrent execution across multiple runners to guarantee full-stack validation.Changes Made
main.pyto allow passing the--runnerargument multiple times (e.g.,--runner pytest --runner vitest).SubprocessSandboxandDockerSandboxto support executing multiple commands concurrently usingasyncioorconcurrent.futures.Impact