Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cross-job cache misses

See original GitHub issue

I have an action setup where a first job creates a cache directory, which is then used by a second jobs which “needs” the first one.

The issue here is that the second job is not picking up the cache that has been created by the first one.

workflow run: https://github.com/airbusgeo/godal/actions/runs/3173227767

relevant logs: In first job:

Run actions/cache@v3
  with:
    path: /optgdal
    key: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2
Cache not found for input keys: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2


#create the cache artifact

Post job cleanup.
/usr/bin/tar --posix -z -cf cache.tgz --exclude cache.tgz -P -C /home/runner/work/godal/godal --files-from manifest.txt
Cache Size: ~28 MB (29473340 B)
Cache saved successfully
Cache saved with key: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2

In second job (ran after first one):

Run actions/cache@v3
  with:
    path: /optgdal
    key: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2
  env:
    GODEBUG: cgocheck=2
Cache not found for input keys: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2

#create the cache artifact , this should not be needed

Post job cleanup.
/usr/bin/tar --posix -z -cf cache.tgz --exclude cache.tgz -P -C /home/runner/work/godal/godal --files-from manifest.txt
Failed to save: Unable to reserve cache with key Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2, another job may be creating this cache. More details: Cache already exists. Scope: refs/heads/main, Key: Linux-install-gdal-release/3.4-aae37644121b0e61978a51cb0d4481abe5363bfcd90970a442fab97c6ccf3ba2, Version: 319ddfe8294d1fea971696ed640f65dff510001254b261687c4d7498b02d8573

Issue Analytics

State:
Created a year ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

tbonfortcommented, Oct 3, 2022

ok found the issue, I was deleting /usr/local/bin as a leftover step in my build script, which is probably where zstd was installed on your runners. Something must have changed on the runners this september concerning the check for zstd and/or the location where it’s installed, as the issue was not present beforehand. Thnaks for your help @aparna-ravindra

0reactions

aparna-ravindracommented, Oct 3, 2022

Yes. I also found the same. Because of this, the cache version while restoring cache v/s saving cache is different. Is there anything in your workflow that alters the zstd package?