From 53842b0f21698b0082fb6e0f229084d7ad884b90 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Sun, 3 May 2026 00:09:02 -0400 Subject: [PATCH] =?UTF-8?q?ci(test-web):=20drop=20npm=20cache=20restore=20?= =?UTF-8?q?=E2=80=94=20setup-node=20was=20burning=204m41s?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Forgejo Actions cache server at 172.18.0.27:41161 isn't reachable from the test-web runner container; setup-node sat there waiting for ETIMEDOUT each run. Drop `cache: 'npm'` so the step finishes in seconds. `npm ci` still works deterministically from package-lock.json — net cost is ~10-30s of registry fetch vs. 4m41s of timeout. Restore the cache option once the runner-host network reaches the cache server (separate operator task). --- .forgejo/workflows/test-web.yml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.forgejo/workflows/test-web.yml b/.forgejo/workflows/test-web.yml index c640ae48..5bcef968 100644 --- a/.forgejo/workflows/test-web.yml +++ b/.forgejo/workflows/test-web.yml @@ -29,11 +29,16 @@ jobs: uses: actions/checkout@v4 - name: Setup Node + # `cache: 'npm'` removed — the Forgejo Actions cache server at + # 172.18.0.27:41161 isn't reachable from this runner's container, + # so setup-node spent 4m41s burning the npm cache restore on + # ETIMEDOUT before failing open. npm ci still works deterministically + # from package-lock.json; just re-fetches from the registry on each + # run. Restore the cache option once the runner-host network reaches + # the cache server. uses: actions/setup-node@v4 with: node-version: '22' - cache: 'npm' - cache-dependency-path: web/package-lock.json - name: Install deps run: npm ci