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
I'm experiencing an issue with the S3 Upload task in Azure DevOps that leads to an assertion error in Node.js. The error message I receive is as follows:
Assertion failed: new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309
##[error]Exit code -1073740791 returned from process: file name 'F:\xxxxBackUp\externals\node10\bin\node.exe', arguments '"F:\xxxxxWorkDir_tasks\S3Upload_3a219265-181c-4ed2-9a51-75a7f308f0d5\1.15.0\S3Upload.js"'.
Steps to Reproduce:
1.Trigger the S3 Upload task in an Azure DevOps pipeline.
2.The task fails with the above error message during execution.
Environment:
1.Node.js Version: 10.x (located at F:\xxxxBackUp\externals\node10\bin\node.exe)
2.S3 Upload Task Version: 1.*
3.Operating System: Windows Server 2019
I would appreciate any insights or solutions from the community or maintainers regarding this issue. Has anyone encountered a similar problem or found a workaround?
Thank you for your help!
The text was updated successfully, but these errors were encountered:
I'm experiencing an issue with the S3 Upload task in Azure DevOps that leads to an assertion error in Node.js. The error message I receive is as follows:
Assertion failed: new_time >= loop->time, file c:\ws\deps\uv\src\win\core.c, line 309
##[error]Exit code -1073740791 returned from process: file name 'F:\xxxxBackUp\externals\node10\bin\node.exe', arguments '"F:\xxxxxWorkDir_tasks\S3Upload_3a219265-181c-4ed2-9a51-75a7f308f0d5\1.15.0\S3Upload.js"'.
Steps to Reproduce:
1.Trigger the S3 Upload task in an Azure DevOps pipeline.
2.The task fails with the above error message during execution.
Environment:
1.Node.js Version: 10.x (located at F:\xxxxBackUp\externals\node10\bin\node.exe)
2.S3 Upload Task Version: 1.*
3.Operating System: Windows Server 2019
I would appreciate any insights or solutions from the community or maintainers regarding this issue. Has anyone encountered a similar problem or found a workaround?
Thank you for your help!
The text was updated successfully, but these errors were encountered: