Azure-pipelines-tasks: 'Extract Files' task for Release fails
Environment
Server - VSTS
Agent - Privately hosted
Issue Description
Extract Files task for Release fails
Zip file is 11MB in size and its on a private hosted agent, that is a Windows 2016 Server
Error logs
2018-05-17T21:33:35.1512744Z ##[error]Extraction failed for file: C:VSTS_DeploymentAgentA1_workr1a_Project-ASP.NET-CIdropABCProject.Web.zip
2018-05-17T21:33:35.1522566Z
2018-05-17T21:33:35.1522820Z ERROR: Can't allocate required memory!
atul898
All 10 comments
@stephenmichaelf - sounds familiar?
bryanmacfarlane
on 18 May 2018
Yes. @atul898 We have seen in the past this is caused by the destination files already existing. Do you clear your drop folder before starting?
@bryanmacfarlane The PR to fix this is here. I thought I had made the FF change but it looks like I didn't or didn't push it. Will get this wrapped up and merged today.
stephenmichaelf
on 18 May 2018
@stephenmichaelf Is this still on the radar? Looks like the pull request was approved, just needs some merge work?
lukewis
on 12 Jun 2018
This would be nice to have fixed. Currently we have multiple test projects that we're extracting and they share some dependencies. I think trying to extract these duplicated dependent dlls to the same output directory is what's causing this error because they can't be overwritten. Our workaround is creating an extraction stage for each of our projects, that each output to a different directory.
shawncrabtree
on 10 Jan 2019
Is this bug going to be fixed and merged? It looks like a long pending open issue. Any work arounds on this?
raswinraaj
on 16 Aug 2019
My workaround is to use Bash task and do the unzipping with
unzip -qo mystuff.zip
mikariekkinen
on 6 Nov 2019
Just came across this issue today, release always fails now as it prompts for input before overwriting each file but with the error message after the prompt reading ERROR: Can't allocate required memory!
Will switch to a shell command or something that can handle overwriting files for now but it would be nice if this fix got merged in at some point.
Benalink
on 5 Feb 2020
I am currently suffering from this issue also. I will work around in the shell but this issue should really be fixed. Open for 2 years now :-(
Miles-Davies-HORIBA
on 14 May 2020
I'm also seeing this issue, trying to extract multiple UI test projects into the same destination folder.
AlexA-1976
on 4 Sep 2020
As a workaround, I moved the extract and the subsequent tasks to a different agent job. That solved the issue.
raswinraaj
on 4 Sep 2020
Related issues
divyesh-parikh
路
3Comments
TheRealEdwardCullen
路
3Comments
Mardoxx
路
3Comments
pharring
路
3Comments
MichaelWhiteCodingForFun
路
3Comments
Most helpful comment
This would be nice to have fixed. Currently we have multiple test projects that we're extracting and they share some dependencies. I think trying to extract these duplicated dependent dlls to the same output directory is what's causing this error because they can't be overwritten. Our workaround is creating an extraction stage for each of our projects, that each output to a different directory.