mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-31 19:16:29 +00:00
f702bba63c
Eleven jobs on every push repeated the same three network round-trips before doing any work: download ripgrep from GitHub releases, run astral-sh/setup-uv, then `uv python install 3.11`. The 8 test slices, e2e, lint x2, docker tests, and uv-lockfile-check all paid it, all for identical bytes. Each hop was also a failure mode — the 2026-07-28 slice-5 incident was a transient setup-uv manifest fetch failing a whole job, and pinning the version narrowed that window without closing it. hermes-agent-ci-infra now bakes ripgrep 15.1.0, uv 0.9.28, and CPython 3.11 into nousresearch/nous-gke-runner (same versions, so this is a move not an upgrade), so these steps are pure overhead. Remove them. The wheel cache is the one part of setup-uv still worth having: it is per-workspace, not per-image, and without it `uv sync` re-downloads and re-builds every wheel — the toolchain would be faster to set up and the sync dramatically slower, a net loss. Replace `enable-cache: true` with a small .github/actions/uv-cache composite doing the same actions/cache on ~/.cache/uv, keyed on pyproject.toml + uv.lock. runner.arch is in the key because the cache holds built wheels and docker.yml runs on arm64 too; the restore-keys prefix means a stale hit still saves most of the download, and `uv sync --locked` re-resolves from uv.lock regardless so a partial hit cannot produce a wrong environment. lint.yml and uv-lockfile-check.yml only `uv tool install` / `uv lock --check` and never build a project venv, so they drop the setup step without needing the cache action at all. Verified against the built image, running as the `runner` user with `--network none` so nothing can silently re-download: rg 15.1.0, uv 0.9.28, and `uv python find 3.11` all resolve. With hermes-agent's real pyproject.toml and uv.lock and no setup step of any kind, `uv sync --locked --python 3.11 --extra dev` completes in 3s into a working 3.11.14 venv. actionlint is clean (the remaining arc-runner-set and SC2016 warnings are pre-existing on main). Depends on the image change landing first: pods pull :latest on start, so merging this before the image is pushed breaks every runner. |
||
|---|---|---|
| .. | ||
| detect-changes | ||
| get-app-token | ||
| nix-setup | ||
| profile | ||
| retry | ||
| uv-cache | ||