Enable caching of virtual environment install #28
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.
Normally poetry installs a project into a randomiish directory of the sort:
/home/runner/.cache/pypoetry/virtualenvs/matrix-synapse-pswDeSvb-py3.13
The tough part there is the hashy looking code and the python version change with each version of python. Since the cache is keyed by python version/extras installed/hash of poetry.lock file, it seems fine to just install the dependencies and project into a known 'never changing' spot, like the
.venv
directory inside the project.Seems to save about 30 seconds to a minute in some 'ad-hoc' testing of installing during several synapse CI test runs