autoresearch.yml's "Set up Python venv" step runs pip install torch --index-url .../cu130 + pip install -r requirements.txt every run. The [ -d .venv ] guard is meant to reuse the venv, but the self-hosted act_runner checks out into a fresh ~/.cache/act/<hash>/hostexecutor dir each run, so .venv never persists — torch (a large cu130 wheel) is re-downloaded and reinstalled every time. Runs spend several minutes here before any real work.
Options
Cache the venv (or just torch's wheel cache) at a stable host path outside the per-run hostexecutor dir, and point pip's cache / a prebuilt .venv there.
Bake a base image with torch+deps preinstalled and run the job in it (container: / prebuilt runner image).
Use a pip download cache dir on the runner host (PIP_CACHE_DIR at a stable path) so at least the wheel isn't re-downloaded.
Source: Autoresearch Loop bring-up, 2026-06-29. Low priority (correctness is fine), but every Phase-A run pays the tax.
## Problem
`autoresearch.yml`'s "Set up Python venv" step runs `pip install torch --index-url .../cu130` + `pip install -r requirements.txt` every run. The `[ -d .venv ]` guard is meant to reuse the venv, but the self-hosted act_runner checks out into a **fresh `~/.cache/act/<hash>/hostexecutor` dir each run**, so `.venv` never persists — torch (a large cu130 wheel) is re-downloaded and reinstalled every time. Runs spend several minutes here before any real work.
## Options
- Cache the venv (or just torch's wheel cache) at a stable host path outside the per-run hostexecutor dir, and point pip's cache / a prebuilt `.venv` there.
- Bake a base image with torch+deps preinstalled and run the job in it (`container:` / prebuilt runner image).
- Use a pip download cache dir on the runner host (`PIP_CACHE_DIR` at a stable path) so at least the wheel isn't re-downloaded.
Source: Autoresearch Loop bring-up, 2026-06-29. Low priority (correctness is fine), but every Phase-A run pays the tax.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
autoresearch.yml's "Set up Python venv" step runspip install torch --index-url .../cu130+pip install -r requirements.txtevery run. The[ -d .venv ]guard is meant to reuse the venv, but the self-hosted act_runner checks out into a fresh~/.cache/act/<hash>/hostexecutordir each run, so.venvnever persists — torch (a large cu130 wheel) is re-downloaded and reinstalled every time. Runs spend several minutes here before any real work.Options
.venvthere.container:/ prebuilt runner image).PIP_CACHE_DIRat a stable path) so at least the wheel isn't re-downloaded.Source: Autoresearch Loop bring-up, 2026-06-29. Low priority (correctness is fine), but every Phase-A run pays the tax.