pinecrew / pined-django / 33504784247

95%

push

github

ci: a cache key per job, so they stop racing for one

Eight of eleven jobs reported `Unable to reserve cache … another job may be
creating this cache`. `setup-uv` builds its key from the runner, the python and
a hash of `cache-dependency-glob`, and nothing in that tells one matrix cell
from another — so the three cells of a python, plus `lint` and
`test (lowest direct)` on 3.12, all reach for the same entry at once and one
wins.

Harmless, and it had already stopped: the three keys are populated now, so the
next run restores rather than saves. But it comes back whenever the key is new,
and the key is taken over `pyproject.toml` since `uv.lock` stopped being
tracked — which is to say every branch that touches a dependency would have
brought the eight warnings back with it.

`cache-suffix` gives each job its own. The entries are 3.7 MB apiece, so nine
of them cost less than one of the entries the old configuration was leaving
behind.

229 of 250 branches covered (91.6%)

Branch coverage included in aggregate %.

1297 of 1360 relevant lines covered (95.37%)

0.95 hits per line