New packages are not being pushed to cache, when using GitHub Actions
srid opened this issue · comments
In the neuron project, a PR just got merged that introduced changes to some dependencies: srid/neuron#315
Per the action run, cachix did seem to push the new ones (notably pandoc, but also skylighting) as one would expect.
However, once the PR got merged to master in srid/neuron@76fc3e4 - the new binaries from cache were not used; and they were rebuilding again.
The same issue happens on subsequent commits on master, such as this one srid/neuron@0b15fdf - and as you can see the build took over 30 mins, building pandoc and friends.
It looks like the cachix push step of the action did not really push all the binaries. That or, something has gone wrong in the cachix server?
Hey @srid, this was fixed yesterday. There was a bug with upstream caches, since Cachix verifies that it has the full closure before it serves the narinfo (due to a Nix bug) and with upstream caches it doesn't have the full closure. So now the exception for those is added and everything should be back to working.