The Gitea Actions cache backend on this instance is not enabled, or is misconfigured, or jobs can't reach it. Either way, actions/cache@v3 is effectively a no-op, which is why cache: 'pip' is not producing the speedup PR #15 (ci: speed up python-package.yml from ~13min to ~3-4min) is hoping for.
Symptom
PR #15 enabled cache: 'pip' with cache-dependency-path: requirements.txt, requirements-dev.txt on actions/setup-python@v5.
On a fresh run, pip install should download deps once and cache them; subsequent runs (or other jobs in the same matrix) should hit the cache. Observed: cache is not working -- either every job does the full install, or the job hangs on the cache write step (tar --posix -cf cache.tzst ...).
for many minutes, the cache backend is reachable but slow. If jobs don't even attempt tar, cache is not configured at all.
What needs to happen
Verify the Gitea Actions cache backend is configured in app.ini on the gitea instance ([cache] section, or wherever gitea exposes it).
If it's enabled, check the storage backend (filesystem? S3? local?). The odroid host might be running on slow storage (SD card? NFS over slow link?). PR #15 in admin/brencher hit this on its reference run #14.
If it's not enabled, enable it and pick a backend that gives reasonable write throughput.
Related
admin/brencher#15 -- the PR that tried to use cache and discovered this
## What
The Gitea Actions cache backend on this instance is not enabled, or is misconfigured, or jobs can't reach it. Either way, `actions/cache@v3` is effectively a no-op, which is why `cache: 'pip'` is not producing the speedup PR #15 (`ci: speed up python-package.yml from ~13min to ~3-4min`) is hoping for.
## Symptom
- PR #15 enabled `cache: 'pip'` with `cache-dependency-path: requirements.txt, requirements-dev.txt` on `actions/setup-python@v5`.
- On a fresh run, `pip install` should download deps once and cache them; subsequent runs (or other jobs in the same matrix) should hit the cache. Observed: cache is not working -- either every job does the full install, or the job hangs on the cache write step (`tar --posix -cf cache.tzst ...`).
- See admin/brencher#15 for the original optimization PR.
## Verify
```bash
# check Gitea config: is cache enabled?
curl -sS -H "Authorization: token $GITEA_TOKEN" \
https://gitea.rudolf.keenetic.link/api/v1/repos/admin/brencher/actions/runs/14/jobs \
| python3 -c ... # tail logs of any failing/slow job -- look for "Cache not found"
# or "tar ... cache.tzst ..." hanging
```
If jobs tail with:
```
[command]/usr/bin/tar --posix -cf cache.tzst --exclude cache.tzst ...
```
for many minutes, the cache backend is reachable but slow. If jobs don't even attempt `tar`, cache is not configured at all.
## What needs to happen
1. Verify the Gitea Actions cache backend is configured in `app.ini` on the gitea instance (`[cache]` section, or wherever gitea exposes it).
2. If it's enabled, check the storage backend (filesystem? S3? local?). The odroid host might be running on slow storage (SD card? NFS over slow link?). PR #15 in admin/brencher hit this on its reference run #14.
3. If it's not enabled, enable it and pick a backend that gives reasonable write throughput.
## Related
- admin/brencher#15 -- the PR that tried to use cache and discovered this
- skills/gitea/references/actions-cache-stall.md -- diagnostic cheatsheet
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
The Gitea Actions cache backend on this instance is not enabled, or is misconfigured, or jobs can't reach it. Either way,
actions/cache@v3is effectively a no-op, which is whycache: 'pip'is not producing the speedup PR #15 (ci: speed up python-package.yml from ~13min to ~3-4min) is hoping for.Symptom
cache: 'pip'withcache-dependency-path: requirements.txt, requirements-dev.txtonactions/setup-python@v5.pip installshould download deps once and cache them; subsequent runs (or other jobs in the same matrix) should hit the cache. Observed: cache is not working -- either every job does the full install, or the job hangs on the cache write step (tar --posix -cf cache.tzst ...).Verify
If jobs tail with:
for many minutes, the cache backend is reachable but slow. If jobs don't even attempt
tar, cache is not configured at all.What needs to happen
app.inion the gitea instance ([cache]section, or wherever gitea exposes it).Related