Question, Bug, or Feature?
Type: Bug
Enter Task Name: Node.js tool installer (v0)
Server - Azure Pipelines
Agent - Hosted
Using the Node.js tool installer task to install Node 8.9.2 and getting an error at the beginning when trying to open the archive. After retrying the build that has this task, this task works sometimes. The build that uses this task and this specific task have not been modified in the build definition and we have not seen this issue before. I did see that this task was recently changed about 9 days ago (according to the commit history).
##[section]Starting: Use Node 8.9.2
==============================================================================
Task : Node.js tool installer
Description : Finds or downloads and caches the specified version spec of Node.js and adds it to the PATH
Version : 0.153.1
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/node-js
==============================================================================
Downloading: https://nodejs.org/dist/v8.9.2/node-v8.9.2-win-x64.7z
Extracting archive
[command]d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe x -bb1 -bd -sccUTF-8 d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009
7-Zip (r) 18.05 (x86) : Igor Pavlov : Public domain : 2018-04-30
Scanning the drive for archives:
1 file, 2195200 bytes (2144 KiB)
Extracting archive: d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009
ERROR: d:\a\_temp\c84e3231-3e9b-4d3d-86e4-21481127e009
Can not open the file as archive
Can't open as archive: 1
Files: 0
Size: 0
Compressed: 0
##[error]d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe failed with return code: 2
##[section]Finishing: Use Node 8.9.2
d:\a\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.153.1\7zr.exe failed with return code: 2
The same thing is happening to us for Node v12.6.0 _(using same Task and 0.* version)_.
Is this new today? Node is having issues on their end, I strongly suspect that's what this is from.
Issue here - https://github.com/nodejs/build/issues/1993
There's unfortunately not anything we can do on our end. I'd recommend retrying builds (I know its annoying, I'm equally annoyed 馃槄). If you use a private agent, it will cache the version of node you're using.
Also, note that the changes to this task you referenced haven't been deployed yet, so that's a red herring
Thanks @damccorm ! That makes sense. We will close this issue.
Although this may not be much help.
I've encountered the same issue, with 2 builds failing CI check in Azure in quick succession. But the 3rd time worked fine.
Seems to be a case of retrying builds until it passes. (Although this is hardly an ideal solution)
Starting happen to us today, did anything change?
Starting happen to us today, did anything change?
Seeing the same issue today.
Nothing changed on our end - looks like another node issue - https://github.com/nodejs/build/issues/2263
Most helpful comment
Starting happen to us today, did anything change?