ci: drop cache: setting in setup-go / setup-node #5

2026-05-14T04:39:36Z

developer commented

2026-05-14 04:39:36 +00:00

What

Turns cache: true (setup-go) and cache: pnpm (setup-node) into cache: false in every workflow.

Why

Both settings 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 and persist between jobs without any plumbing:

~/go/pkg/mod (760 MB)
~/.cache/go-build (1.6 GB)
~/.local/share/pnpm (241 MB)
~/.cache/ms-playwright (chromium + webkit warm)

The --mount=type=cache directives in our Dockerfiles continue to give the same effect for docker build steps.

Expected impact

ui-test: stop the zombie reserveCache loop that historically pushed run #14 to 12m+. ui-test #37 (rerun with warm host caches) clocked 2m03s; this should make that a stable baseline.
go-unit / integration: a few seconds of savings on each run.
dev-deploy: marginal — its bottleneck is docker build, not setup-*.

TODO (not in this PR)

Fix the Gitea Actions cache service so we can opt back into it later if we want cross-host caching.

## What Turns `cache: true` (setup-go) and `cache: pnpm` (setup-node) into `cache: false` in every workflow. ## Why Both settings 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` and persist between jobs without any plumbing: - `~/go/pkg/mod` (760 MB) - `~/.cache/go-build` (1.6 GB) - `~/.local/share/pnpm` (241 MB) - `~/.cache/ms-playwright` (chromium + webkit warm) The `--mount=type=cache` directives in our Dockerfiles continue to give the same effect for `docker build` steps. ## Expected impact - ui-test: stop the zombie reserveCache loop that historically pushed run #14 to 12m+. ui-test #37 (rerun with warm host caches) clocked **2m03s**; this should make that a stable baseline. - go-unit / integration: a few seconds of savings on each run. - dev-deploy: marginal — its bottleneck is docker build, not setup-*. ## TODO (not in this PR) Fix the Gitea Actions cache service so we can opt back into it later if we want cross-host caching.

developer added 1 commit 2026-05-14 04:39:37 +00:00

ci: drop cache: setting in setup-go/setup-node

Tests · Go / test (push) Successful in 2m21s

Details

Tests · UI / test (push) Successful in 2m22s

Details

Tests · Go / test (pull_request) Successful in 3m14s

Details

Tests · Integration / integration (pull_request) Successful in 1m37s

Details

Tests · UI / test (pull_request) Successful in 2m7s

Details

8058f26397

`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>

developer merged commit fd071260ec into development

2026-05-14 04:47:56 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/galaxy-game#5