You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the enhancement
When saving multiple caches, the temporary tar files created for each upload are left on the filesystem. With large caches the wasted space can be the difference between a successful run and an IOException: No space left on device error.
Consider a workflow that needs to save four separate caches containing 1GB each. The first call to saveCache creates a temporary archive, which could be up to 1GB in size (for uncompressible data). That temporary file is never deleted, so the subsequent calls have 1GB less SSD space available. By the end of the upload process there could be 4GB of wasted space that's unavailable for the rest of the workflow.
restoreCache already has a "finally" block to delete each temporary archive after its contents have been extracted. If this were implemented for saveCache the scenario above would use at most 1GB of space temporarily during upload. Once uploads were complete there would be no temporary files left on the SSD.
The text was updated successfully, but these errors were encountered:
Describe the enhancement
When saving multiple caches, the temporary tar files created for each upload are left on the filesystem. With large caches the wasted space can be the difference between a successful run and an
IOException: No space left on device
error.Consider a workflow that needs to save four separate caches containing 1GB each. The first call to saveCache creates a temporary archive, which could be up to 1GB in size (for uncompressible data). That temporary file is never deleted, so the subsequent calls have 1GB less SSD space available. By the end of the upload process there could be 4GB of wasted space that's unavailable for the rest of the workflow.
restoreCache
already has a "finally" block to delete each temporary archive after its contents have been extracted. If this were implemented forsaveCache
the scenario above would use at most 1GB of space temporarily during upload. Once uploads were complete there would be no temporary files left on the SSD.The text was updated successfully, but these errors were encountered: