Open jimsynz opened 11 months ago
I had the same problem, you need to set --backend.operation-timeout
to fix it.
Edit: One remaining problem is that the cache is split into 5mb files, which probably causes a lot of overhead when dealing with a few gb of data. Would be nice if that could be configured to a higher file size.
Observed Behaviour
I have a job which is trying to cache about 8GB of data rather than download it again from the internet. Sadly it fails with the following error:
See the entire job here: https://drone.harton.nz/bivouac/bivouac_system_x86_64/35/1/11
Steps to Reproduce
Expected Behaviour
It should push the cache to the remote storage (even if it takes a long time).