Repository navigation
Windows permanently-failing-in-CI hosts marked offline #2145
Description
Activity
It seems to be spreading...now adding:
- test-azure_msft-win10_vs2019-x64-1
- test-azure_msft-win10_vcbt2015-x64-3
- test-rackspace-win2008r2_vs2017-x64-3
- test-rackspace-win2008r2_vs2017-x64-2
- test-rackspace-win2012r2_vs2019-x64-1
- test-rackspace-win2012r2_vs2017-x64-3
- test-rackspace-win2012r2_vs2013-x64-2
- test-azure_msft-win2016_vs2017-x64-4
- test-azure_msft-win2016_vs2017-x64-5
- test-azure_msft-win2016_vs2017-x64-1
Hoping there are still some windows hosts left to run tests...
/ping @joaocgreis
- win2008r2_vs2017-x64-3
This was apparently caused by an old version of nodejs/node#31505 leaving behind files that could not be removed by git clean.
The PR is now fixed, the computers clean and back online, and windows-fanned back to green.
@Trott thanks for taking the machines offline! Another thing that might or might not help but should be harmless is to run https://ci.nodejs.org/view/All/job/git-clean-windows/ and https://ci.nodejs.org/view/All/job/windows-update-reboot/ with force reboot.
Another thing that might or might not help but should be harmless is to run https://ci.nodejs.org/view/All/job/git-clean-windows/ and https://ci.nodejs.org/view/All/job/windows-update-reboot/ with force reboot.
I didn't know those existed! I'll try them next time I'm completely flummoxed by a Windows issue and have no idea what to do. :-D
Thanks!
- Reacted by Richard Lau
To get CI working, I marked four Windows hosts as offline. They were failing CI tests consistently.
Not sure what the right thing to do to get them back online is.