revert(ci): remove cache steps until runner cache server works #107

2026-07-07T17:52:16+02:00

ffaerber commented

2026-07-07 17:52:16 +02:00

The ci-runner cache backend is unreachable — actions/cache restore/save time out (getCacheEntry failed: Request timeout: /_apis/artifactcache/cache). With no reachable backend, each cache op just blocks ~20s before failing, so these steps add latency to every run for zero benefit.

Removing the two actions/cache steps (and the now-unused top-level OPENCODE_VERSION env). The harmless "skip opencode re-download if the pinned binary is already present" logic in install-opencode.sh stays — it helps on a persistent runner and never blocks.

Re-add caching once the runners act_runner cache server (cache.host` in its config.yaml) is reachable from job containers.

The `ci-runner` cache backend is unreachable — `actions/cache` restore/save time out (`getCacheEntry failed: Request timeout: /_apis/artifactcache/cache`). With no reachable backend, each cache op just blocks ~20s before failing, so these steps *add* latency to every run for zero benefit. Removing the two `actions/cache` steps (and the now-unused top-level `OPENCODE_VERSION` env). The harmless "skip opencode re-download if the pinned binary is already present" logic in `install-opencode.sh` stays — it helps on a persistent runner and never blocks. Re-add caching once the runner`s `act_runner` cache server (`cache.host` in its config.yaml) is reachable from job containers.

ffaerber added 1 commit 2026-07-07 17:52:16 +02:00

revert(ci): remove actions/cache steps — cache backend unreachable, times out and slows runs

ci / lint (pull_request) Successful in 11s

Details