Open ain opened 3 years ago
I agree this is weird, but do you really need to install this package inside GitHub Actions? I would guess it already worked out of the box.
@papb would be glad to avoid, but it seems node-sass
installation failure bound to node-gyp
is the bottleneck here:
npm ERR! gyp ERR! System Windows_NT 10.0.17763
647
npm ERR! gyp ERR! command "C:\\hostedtoolcache\\windows\\node\\15.2.0\\x64\\node.exe" "D:\\a\\smartbanner.js\\smartbanner.js\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
648
npm ERR! gyp ERR! cwd D:\a\smartbanner.js\smartbanner.js\node_modules\node-sass
649
npm ERR! gyp ERR! node -v v15.2.0
650
npm ERR! gyp ERR! node-gyp -v v3.8.0
651
npm ERR! gyp ERR! This is a bug in `node-gyp`.
652
npm ERR! gyp ERR! Try to update node-gyp and file an Issue if it does not help:
653
npm ERR! gyp ERR! <https://github.com/nodejs/node-gyp/issues>
654
npm ERR! Build failed with error code: 7
A note worth making: running without npm install --global --production windows-build-tools
and directly against npm install
succeeds when on Node.js v14.x
, but node-gyp
install fails on Node.js v15.x
.
Having same issues, install is in endless loop
Same issue when using Windows Server 2016
I also tried to pre-install Python 2.7. Now there is an endless loop continuously printing
------------------- Python --------------------
Python 2.7.18 is already installed, not installing again.---------- Visual Studio Build Tools ----------
2021-03-18T19:28:15 : Verbose : Calling SetupEngine.Installer.EvaluateInstallParameters. [channelId: VisualStudio.15.Release, productId: Microsoft.VisualStudio.Product.BuildTools, installationPath: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools', languages: 'en-US' selectedPackageReferences.length: 13]
2021-03-18T19:28:15 : Verbose : SetupEngine.Installer.EvaluateInstallParameters succeeded. [channelId: VisualStudio.15.Release, productId: Microsoft.VisualStudio.Product.BuildTools, installationPath: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools', languages: 'en-US' selectedPackageReferences.length: 13]
2021-03-18T19:28:15 : Verbose : Calling SetupEngine.Installer.EvaluateInstallParameters. [channelId: VisualStudio.15.Release, productId: Microsoft.VisualStudio.Product.BuildTools, installationPath: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools', languages: 'en-US' selectedPackageReferences.length: 13]
2021-03-18T19:28:15 : Verbose : SetupEngine.Installer.EvaluateInstallParameters succeeded. [channelId: VisualStudio.15.Release, productId: Microsoft.VisualStudio.Product.BuildTools, installationPath: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools', languages: 'en-US' selectedPackageReferences.length: 13]
2021-03-18T19:28:15 : Verbose : Calling SetupEngine.Installer.InstallProduct. [channelId: VisualStudio.15.Release, productId: Microsoft.VisualStudio.Product.BuildTools, installationPath: 'C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools']
Steps to reproduce
Run installation on
Microsoft Windows Server 2019
(e.g. on GitHub Actions)$ npm install --global --production windows-build-tools
What happens
Before cancelling the workflow, it ran in the loop for 11 min.
What should happen
Installation should succeed.