Repository navigation
nasm installation fails from Chocolatey #39038
Description
The coverage-windows and build-windows workflows seem to be failing consistently due to nasm.us being unavailable for Chocolatey (ie. choco install ..), and blocks GitHub checks for staging branches, release branches, and master. With some quick googling, it appears that this is something that happens with the host sometimes, but it can be fixed by using Chocolatey's CDN or having an internally hosted nasm.
- Test:
coverage-windowsandbuild-windowsGitHub workflows - Platform: Windows
- Console Output:
Run choco install nasm
Chocolatey v0.10.15
Installing the following packages:
nasm
By installing you accept licenses for the packages.
Progress: Downloading nasm 2.14.02... 15%
Progress: Downloading nasm 2.14.02... 49%
Progress: Downloading nasm 2.14.02... 82%
Progress: Downloading nasm 2.14.02... 100%
nasm v2.14.02 [Approved]
nasm package files install completed. Performing other installation steps.
Attempt to get headers for https://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win64/nasm-2.14.02-installer-x64.exe failed.
The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win64/nasm-2.14.02-installer-x64.exe'. Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote server"
Downloading nasm 64 bit
from 'https://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win64/nasm-2.14.02-installer-x64.exe'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://www.nasm.us/pub/nasm/releasebuilds/2.14.02/win64/nasm-2.14.02-installer-x64.exe'. Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote server"
This package is likely not broken for licensed users - see https://chocolatey.org/docs/features-private-cdn.
The install of nasm was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\nasm\tools\chocolateyInstall.ps1'.
Activity
targos commentedon Jun 15, 2021
It's not the first time I see this happen... Sometimes https://www.nasm.us/ is just down.
bl-ue commentedon Jun 15, 2021
Yeah, I'm pretty sure that this has happened to me on a non-node-related score at some point in the past too 🤔
danielleadams commentedon Jun 28, 2021
Should I close this?
targos commentedon Aug 9, 2021
As you want. If you think it is worth fixing this on our side, it's better to keep it open. Otherwise we can close.
danielleadams commentedon Aug 17, 2021
Looks like a similar error has happened again: https://github.com/nodejs/node/pull/39782/checks?check_run_id=3344509225 😕 I'll keep it open for now.
shnooshnoo commentedon Dec 19, 2023
hi @danielleadams I was going through Windows-related issues and noted this one. Both coverage-windows and build-windows workflows have been green lately (coverage windows is actually disabled atm). The problem back then might've been caused by a very early Chocolatey version (0.10), which is very different to what we have now (2.2.2).
Considering the above, looks like we can close this issue now?
StefanStojanovic commentedon Jul 17, 2024
Since this is no longer active, and there has been no answer since the last comment, I'll close this. If you still experience the same issue, please reopen this issue or open a new one.