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-windows and build-windows GitHub 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'.
The
coverage-windowsandbuild-windowsworkflows seem to be failing consistently due tonasm.usbeing 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 hostednasm.coverage-windowsandbuild-windowsGitHub workflowshttps://github.com/nodejs/node/runs/2826101554
https://github.com/nodejs/node/pull/39031/checks?check_run_id=2826221528
https://github.com/nodejs/node/pull/39031/checks?check_run_id=2826221630