Right now running an eval (e.g., using the SWE-agent evaluation/evaluation.py script) runs in such a way that a temporary conda environment is created each time you run an eval. It seems like the conda environments could be created once per repo/version, and then reused again and again across different evaluations.
Potential Solutions
One way to do this (for which I'll attach a PR) is to simply configure a reaonable path_conda in the eval args; e.g.,
Describe the feature
Right now running an eval (e.g., using the SWE-agent evaluation/evaluation.py script) runs in such a way that a temporary conda environment is created each time you run an eval. It seems like the conda environments could be created once per repo/version, and then reused again and again across different evaluations.
Potential Solutions
One way to do this (for which I'll attach a PR) is to simply configure a reaonable
path_conda
in the eval args; e.g.,