-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Exit 57005 StackOverflowException using AzureFileCopy@6 #20221
Comments
Hi @directhex, is this issue still persists? |
Actually, I haven't seen this failure personally in August. Let me check in with a Teams chat w/ other people suffering from related issues. |
The issue still exists |
Hi @directhex
Please share these details in order to investigate further. |
I haven't had the issues since July 29th, on a daily job. I can't guarantee I haven't just been very lucky, but from my perspective, I'm no longer experiencing an issue. |
@Schniefel Could you pls let us know if you are still facing this issue or not? If yes then pls do share the details. |
I upload big files. After every ~56m:
|
@directhex , @onetocny By any chance do you guys have any solution to this? Because I am also facing the same issue when running my release pipeline via 1ES.
|
@Rudresh-Infy The issue was probably fixed by #20575. We will start releasing fixed version next week. In the mean time it should be possible to mitigate the issue by prepending following task in your pipeline: - task: PowerShell@2
inputs:
targetType: 'inline'
script: |
Install-Module Az.Accounts -Force -AllowClobber -ErrorAction Stop -SkipPublisherCheck
Import-Module Az.Accounts -Global -PassThru -Force
Update-AzConfig -CheckForUpgrade $false |
Hi Ondrej,
Thank you for your reply.
I have added as suggested but still getting the same error. As you can see in the below screenshot.
***@***.***
***@***.***
Kindly please suggest.
Thank you!
Regards,
Rudresh Singh
From: Ondřej Netočný ***@***.***>
Sent: 11 November 2024 12:15
To: microsoft/azure-pipelines-tasks ***@***.***>
Cc: Rudresh Singh (INFOSYS LIMITED) ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/azure-pipelines-tasks] [BUG]: Exit 57005 StackOverflowException using ***@***.*** (Issue #20221)
@Rudresh-Infy<https://github.com/Rudresh-Infy> The issue was probably fixed by #20575<#20575>. We will start releasing fixed version next week.
-
Reply to this email directly, view it on GitHub<#20221 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMYOLEJZCBCO35LMNVEYBV32ABG5LAVCNFSM6AAAAABLUWT7XKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGM3DCNBYGM>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Thank you, It's fixed now.
Thank you!
Regards,
Rudresh Singh
From: Ondřej Netočný ***@***.***>
Sent: 11 November 2024 12:15
To: microsoft/azure-pipelines-tasks ***@***.***>
Cc: Rudresh Singh (INFOSYS LIMITED) ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/azure-pipelines-tasks] [BUG]: Exit 57005 StackOverflowException using ***@***.*** (Issue #20221)
@Rudresh-Infy<https://github.com/Rudresh-Infy> The issue was probably fixed by #20575<#20575>. We will start releasing fixed version next week.
-
Reply to this email directly, view it on GitHub<#20221 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BMYOLEJZCBCO35LMNVEYBV32ABG5LAVCNFSM6AAAAABLUWT7XKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGM3DCNBYGM>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
New issue checklist
Task name
AzureFileCopy
Task version
6.243.0
Issue Description
We've been experiencing intermittent issues with StackOverflowException in this task. It seems very likely to be related to #20156
We've experienced this failure on 6.243.0, 6.242.10, and 6.242.6 (I can't find it happening on older versions, but our job is only daily so that's not a guarantee)
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2022
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: