-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows CI issues on v10.x #2070
Comments
Marked the following offline with a reason linking back to this issue: |
@joaocgreis is it possible that the work being done in #1996 is somehow related? |
@richardlau thanks, taking the machines offline is the right thing to do in this case. I'll take a look ASAP and try to figure out what's happening there. In any case, those two machines are going away very soon. While I'd rather understand what's happening there, we've had other issues that only happen in specifics machines and that's why I'm refreshing all of them. |
Should be fixed: nodejs/node#30639 (comment) |
Based on looking at nodejs/node#30639 (comment),
I suspect something specific about
test-azure_msft-win10-x64-3
andtest-azure_msft-win2016-x64-3
may be causing the test failures seen on v10.x.Can we mark these two as offline in Jenkins temporarily so that I can do a test CI to see if this is the case?
The text was updated successfully, but these errors were encountered: