2 Commits

Author SHA1 Message Date
developer fd071260ec Merge pull request #5: drop cache: setting in setup-go / setup-node
Deploy · Dev / deploy (push) Successful in 31s
Tests · Go / test (push) Successful in 1m44s
Tests · Integration / integration (push) Successful in 1m42s
Tests · UI / test (push) Successful in 2m11s
Avoids the zombie reserveCache retries against the unreachable Gitea Actions cache service on :43513. Host-mode runner keeps caches warm in $HOME without needing actions/cache plumbing.
2026-05-14 04:47:56 +00:00
Ilia Denisov 8058f26397 ci: drop cache: setting in setup-go/setup-node
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>
2026-05-14 06:39:22 +02:00
5 changed files with 24 additions and 10 deletions
+7 -3
View File
@@ -40,7 +40,8 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
cache: true # See go-unit.yaml for why `cache: true` is disabled.
cache: false
- name: Set up pnpm - name: Set up pnpm
uses: pnpm/action-setup@v4 uses: pnpm/action-setup@v4
@@ -51,8 +52,11 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
cache: pnpm # `cache: pnpm` pushes the pnpm store through the Gitea
cache-dependency-path: ui/pnpm-lock.yaml # Actions cache service which is currently unreachable
# (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
# store lives in ~/.local/share/pnpm and persists between
# jobs without any action plumbing.
- name: Install UI dependencies - name: Install UI dependencies
working-directory: ui working-directory: ui
+7 -1
View File
@@ -46,7 +46,13 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
cache: true # `cache: true` here pushes/pulls archives through the Gitea
# Actions cache service at 192.168.0.222:43513. That endpoint
# currently does not answer, and the action wastes minutes
# per run on reserveCache retries. In host-mode the real
# caches live in $HOME (~/go/pkg/mod, ~/.cache/go-build) and
# persist between jobs without any actions/cache plumbing.
cache: false
- name: Run Go tests - name: Run Go tests
# client/ is the deprecated Fyne client; excluded from CI per # client/ is the deprecated Fyne client; excluded from CI per
+2 -1
View File
@@ -53,7 +53,8 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
cache: true # See go-unit.yaml for why `cache: true` is disabled.
cache: false
- name: Run integration suite - name: Run integration suite
# `make integration` precleans leftover docker-compose state and # `make integration` precleans leftover docker-compose state and
+3 -3
View File
@@ -37,7 +37,8 @@ jobs:
uses: actions/setup-go@v5 uses: actions/setup-go@v5
with: with:
go-version-file: go.work go-version-file: go.work
cache: true # See go-unit.yaml for why `cache: true` is disabled.
cache: false
- name: Set up pnpm - name: Set up pnpm
uses: pnpm/action-setup@v4 uses: pnpm/action-setup@v4
@@ -48,8 +49,7 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
cache: pnpm # See dev-deploy.yaml for why `cache: pnpm` is disabled.
cache-dependency-path: ui/pnpm-lock.yaml
- name: Resolve image tag - name: Resolve image tag
id: tag id: tag
+5 -2
View File
@@ -37,8 +37,11 @@ jobs:
uses: actions/setup-node@v4 uses: actions/setup-node@v4
with: with:
node-version: 22 node-version: 22
cache: pnpm # `cache: pnpm` pushes the pnpm store through the Gitea
cache-dependency-path: ui/pnpm-lock.yaml # Actions cache service which is currently unreachable
# (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
# store lives in ~/.local/share/pnpm and persists between
# jobs without any action plumbing.
- name: Install npm dependencies - name: Install npm dependencies
working-directory: ui working-directory: ui