Closed LebedevRI closed 1 year ago
There appears to be some cache consistency issue, at least when the cache is being restored on a different OS it was created on.
Example:
Cache saved with key: coverage-2ec84780854ccde800df79c4b10e51bf802f1232-macOS
needs
Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: coverage-2ec84780854ccde800df79c4b10e51bf802f1232-macOS
Rerunning the second job does not change the outcome. But this is working in principle, e.g. https://github.com/darktable-org/rawspeed/actions/runs/4227408578/jobs/7342201975#step:31:19
Yep, that sounds like it. Pretty horrible UX though. Thanks.
There appears to be some cache consistency issue, at least when the cache is being restored on a different OS it was created on.
Example:
Cache saved with key: coverage-2ec84780854ccde800df79c4b10e51bf802f1232-macOS
https://github.com/darktable-org/rawspeed/actions/runs/4233266783/jobs/7355207131#step:12:13needs
), fails to find it:Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: coverage-2ec84780854ccde800df79c4b10e51bf802f1232-macOS
https://github.com/darktable-org/rawspeed/actions/runs/4233266783/jobs/7355214037#step:31:15Rerunning the second job does not change the outcome. But this is working in principle, e.g. https://github.com/darktable-org/rawspeed/actions/runs/4227408578/jobs/7342201975#step:31:19