-
Notifications
You must be signed in to change notification settings - Fork 15
Issue creating tarball: tar: Failed to clean up compressor #35
Comments
Sorry that you're running into this! My first guess would be that this is a permissions issue and bsdtar (the tar that's bundled with Win10) has very unhelpful error messages. Could you try running the build agent in an elevated command prompt to prove/disprove this? |
I have tried that now, but I still get the same error message. Is there anything else I could do to try to locate the problem? Thanks. |
I've heard other reports of this but I haven't been able to repro it myself. My best guidance at the moment would be to use Azure DevOp's built in Pipeline Caching which is the successor to these tasks. Since you only need to cache a single directory, the built in caching functionality should work like a charm. Based on the build step you shared above, this should work for you. - task: Cache@2
displayName: Cache
inputs:
key: '$(Agent.OS) | yarn | UserManager/yarn.lock'
path: 'UserManager/node_modules'
cacheHitVar: 'PACKAGES_RESTORED' |
Thank you. Switching to the built in Pipeline Caching worked for me. |
@ethanis I have the same issue as @mfahlen and tried switching to using Cache@2, but I run into the problem of it not recognizing ng or nx (nrwl) commands when cached. Any advice on how to recognize those during the pipeline? Tasks:
Error:
Note: setting the cache to node_modules and the install script to "npm install" does work, but I saw that it's not recommended. |
@jamesga1 since you're restoring the You'll still get benefits from caching because you won't be making a network call for each package as each package is resolvable from npm's cache. |
@ethanis , I am having the exact error in our Build pipeline. But we use pool of "Azure Pipelines" and agent specification "windows-2019"
Any hope to troubleshoot this. Note: I also tried using the Pipeline Caching task but feel its very slow and doesn't support pattern matching for folder paths. This is useful since we have "node_modules" in several folders in our solution. |
@temparnak sorry to hear you're running into this! Can you share your build definition and build logs? Note: pattern matching should be coming soon to the official caching tasks 🎉 |
@ethanis Here is the task definition. Have attached the build log.
|
@temparnak nothing in the build logs indicate something that would fail. Unfortunately, I'm not able to reproduce this, so I'm not quite sure how I can help further 😦 Would it be possible to build your project on linux instead? I'm curious if the caching step would succeed there instead. |
Unfortunately, our solution is based on .net framework, I think Linux won't help. On the bright side, I have setup Pipeline Cache task in our build job and it seems to work. Better than no cache, but it can't keep up to the speed of the Artifact Caching task. |
I wish I could help more here, but I'm glad you have at least some caching working! |
I found if pipeline run at Linux os (e.g ubuntu-20.04) was fine, |
I am running the following task on a self-hosted agent with Windows 10, the latest version of Azure CLI (2.1.0), and the latest version of azure-devops extension (0.17.0):
The post-job which is supposed to save artifacts to cache fails with:
This is what's logged by the task when enabling debug output:
"where tar" gives me the following and shouldn't be the issue:
Any idea why this task is failing for me? I appreciate any help.
The text was updated successfully, but these errors were encountered: