Cache Node and the uv binary in CI #420

Merged

robbertbos merged 1 commit from ci-cache-node into main 2026-09-23 21:02:23 +00:00

Conversation 0 Commits 1 Files changed 2 +58 -9

robbertbos commented 2026-09-23 20:27:53 +00:00

Owner

Copy link

A cache hit means CI downloads neither Node nor uv.

• Node (4 jobs): actions/cache keeps ${{ runner.tool_cache }}/node under node-24-<os>. On a hit, setup-node finds Node 24 locally and makes no network call. This is the download that failed frontend-test on #416.
• uv binary (3 jobs): the tarball is cached under uv-dist-<UV_SHA256>. sha256sum -c still runs on every job, cached or not, so the fail-closed pin is unchanged. A Renovate bump changes the sha and with it the key.

How long an entry lasts. Per the runner's own cache server (act/artifactcache/caches.go in forgejo/runner): unused for 7 days, deleted; 30 days after creation, always deleted; the same key saved again keeps only the newest. So a new Node 24 patch release arrives within a month without a date in the key. The cache lives on the runner host.

Not cached, on purpose. apt-get install postgresql and Playwright's --with-deps come from the Ubuntu mirrors, and caching apt packages is fragile. npm packages, Playwright browsers, uv packages and pre-commit envs were already cached.

To check on the first run. Whether Forgejo fills runner.tool_cache: the "Cache Node" step logs the path it saves. The first run is a cache miss and still downloads once.

A cache hit means CI downloads neither Node nor uv. - **Node** (4 jobs): `actions/cache` keeps `${{ runner.tool_cache }}/node` under `node-24-<os>`. On a hit, `setup-node` finds Node 24 locally and makes no network call. This is the download that failed `frontend-test` on #416. - **uv binary** (3 jobs): the tarball is cached under `uv-dist-<UV_SHA256>`. `sha256sum -c` still runs on every job, cached or not, so the fail-closed pin is unchanged. A Renovate bump changes the sha and with it the key. **How long an entry lasts.** Per the runner's own cache server (`act/artifactcache/caches.go` in forgejo/runner): unused for 7 days, deleted; 30 days after creation, always deleted; the same key saved again keeps only the newest. So a new Node 24 patch release arrives within a month without a date in the key. The cache lives on the runner host. **Not cached, on purpose.** `apt-get install postgresql` and Playwright's `--with-deps` come from the Ubuntu mirrors, and caching apt packages is fragile. npm packages, Playwright browsers, uv packages and pre-commit envs were already cached. **To check on the first run.** Whether Forgejo fills `runner.tool_cache`: the "Cache Node" step logs the path it saves. The first run is a cache miss and still downloads once.

robbertbos added 1 commit 2026-09-23 20:27:53 +00:00

Cache Node and the uv binary in CI ... b78fdf273a

setup-node downloaded Node on every run, asking the GitHub API first;
the shared runner IP hits its anonymous rate limit and the fallback
download failed ("API rate limit exceeded", then a TLS disconnect in
frontend-test). The Node tool cache is now kept with actions/cache,
keyed per month so a new patch release still arrives, and setup-node
finds it without any network call.

The uv tarball is cached under its pinned sha256 as the key. The
sha256 check still runs on every job, cached or not, so the
fail-closed anchor is unchanged.

robbertbos force-pushed ci-cache-node from b78fdf273a to 78bf61d59d 2026-09-23 20:30:44 +00:00 Compare

robbertbos force-pushed ci-cache-node from 78bf61d59d to 38d44ea35a 2026-09-23 20:44:11 +00:00 Compare

robbertbos scheduled this pull request to auto merge when all checks succeed 2026-09-23 20:50:13 +00:00

robbertbos force-pushed ci-cache-node from 38d44ea35a to 8f016ada6a 2026-09-23 20:56:00 +00:00 Compare

robbertbos merged commit 8f016ada6a into main 2026-09-23 21:02:23 +00:00

robbertbos deleted branch ci-cache-node 2026-09-23 21:02:23 +00:00

robbertbos referenced this pull request 2026-09-23 21:15:48 +00:00

Make the frontend tests independent of runner load #425

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

help wanted

Need some help

  

invalid

Something is wrong

  

nldd ds

  

question

More information is needed

  

wontfix

This won't be fixed

No labels

bug

duplicate

enhancement

help wanted

invalid

nldd ds

question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

robbertbos/waggle!420

No description provided.