Ilia Denisov
8058f26397
Tests · Go / test (push) Successful in 2m21s
Tests · UI / test (push) Successful in 2m22s
Tests · Go / test (pull_request) Successful in 3m14s
Tests · Integration / integration (pull_request) Successful in 1m37s
Tests · UI / test (pull_request) Successful in 2m7s
`cache: true` (setup-go) and `cache: pnpm` (setup-node) make the actions push and pull tarballs through the Gitea Actions cache service at 192.168.0.222:43513. That endpoint currently does not answer, so every workflow burns minutes per run on reserveCache retries before the action gives up. In host-mode the real caches live under the runner user's $HOME (~/go/pkg/mod, ~/.cache/go-build, ~/.local/share/pnpm, ~/.cache/ms-playwright) and persist between jobs without any actions/cache plumbing. Switching cache: off avoids the zombie retries and uses the local disk caches the runner already has warm. Reviving the cache service is a separate TODO. Until then this is the simpler and faster baseline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>