Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't let tox install a virtualenv during evaluation #171

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

waterson
Copy link
Contributor

@waterson waterson commented Jul 3, 2024

By default, tox will try to create a virtualenv in which to reinstall all of the dependencies. We don't need this level of isolation for SWE-bench, so use the tox-current-env plugin to elide that.

Reference Issues/PRs

Fixes #170.

What does this implement/fix? Explain your changes.

Use the tox-current-env plugin to tell tox not to try to install its own venv.

Any other comments?

🧡 Thanks for contributing!

By default, `tox` will try to create a virtualenv in which to reinstall all of
the dependencies. We don't need this level of isolation for SWE-bench, so use
the `tox-current-env` plugin to elide that.
@ofirpress
Copy link
Collaborator

Thanks Chris!

@john-b-yang
Copy link
Member

Sweet thanks for the catch @waterson! LGTM + merged. Just took a look at an execution log as well and saw the same original behavior.

@john-b-yang john-b-yang merged commit 86f44ee into swe-bench:main Jul 3, 2024
1 check passed
sreekarmolakalapalli pushed a commit to Modelcode-ai/SWE-bench that referenced this pull request Aug 14, 2024
Don't let tox install a virtualenv during evaluation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sphinx-doc instances create an unecessary tox virutalenv during eval
3 participants