cinny

LotusGuild/cinny

Fork 0

...

Author SHA1 Message Date

Author	SHA1	Message	Date
jared	4656f08802	Revert "ci: re-enable npm/node_modules cache — runner cache network fixed" CI / Build & Quality Checks (push) Successful in 1m42s Details CI / Trigger Desktop Build (push) Successful in 12s Details This reverts commit `a631e90ea2`.	2026-08-02 23:23:52 -04:00
jaredandClaude Opus 4.8	a631e90ea2	ci: re-enable npm/node_modules cache — runner cache network fixed CI / Build & Quality Checks (push) Canceled after 4m44s Details CI / Trigger Desktop Build (push) Canceled after 0s Details The act_runner cache server is now reachable from job containers: jobs were landing on isolated per-job docker networks and couldn't reach the runner's cache server on docker0 (getCacheEntry ETIMEDOUT, ~5 min wasted/build). Fixed runner-side by putting the runner + all job containers on a shared dedicated network (`act-cache-net`, runner at 172.30.0.2) and pointing cache.host at it — verified a container on that network reaches the cache port. Restores `cache: npm` on Setup Node and the actions/cache node_modules step (restore + save-on-miss-and-success). Reverts `10270b75` now that the underlying network issue is resolved. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-08-02 23:18:00 -04:00

jared

4656f08802

Revert "ci: re-enable npm/node_modules cache — runner cache network fixed"

CI / Build & Quality Checks (push) Successful in 1m42s

Details

CI / Trigger Desktop Build (push) Successful in 12s

Details

This reverts commit a631e90ea2.

2026-08-02 23:23:52 -04:00

jaredandClaude Opus 4.8

a631e90ea2

ci: re-enable npm/node_modules cache — runner cache network fixed

CI / Build & Quality Checks (push) Canceled after 4m44s

Details

CI / Trigger Desktop Build (push) Canceled after 0s

Details

The act_runner cache server is now reachable from job containers: jobs were
landing on isolated per-job docker networks and couldn't reach the runner's
cache server on docker0 (getCacheEntry ETIMEDOUT, ~5 min wasted/build). Fixed
runner-side by putting the runner + all job containers on a shared dedicated
network (`act-cache-net`, runner at 172.30.0.2) and pointing cache.host at it —
verified a container on that network reaches the cache port.

Restores `cache: npm` on Setup Node and the actions/cache node_modules step
(restore + save-on-miss-and-success). Reverts 10270b75 now that the underlying
network issue is resolved.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-08-02 23:18:00 -04:00

Compare commits

Diff Content Not Available