-
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
Requesting access to debian8-x86 for debugging spooky failures #1207
Comments
SGTM |
@BridgeAR Alas, those are all now 404s.... |
SGTM |
(Ooooohhhhhh...the fact that they're 404s is not important. The fact that they are fully 50% debian8-x86 is the important part. Got it. Sorry for the noise.) |
SGTM |
@nodejs/build What’s the process for this? It would be ideal if I could have some time to look into this over the weekend, if that’s possible at all |
@addaleax |
I think I figured out everything I can in nodejs/node#19903 (comment). I’d like to wait for another opinion or so, but generally I should be done with access here. If somebody else does remove me before that (which is completely fine), please make sure to remove |
Okay, I’ve removed my own access now. Thanks everyone! |
Hi everyone! If it’s cool with you, I’d like to try and dig into those spooky no-stack-trace, no-error, no-nothing failures we’ve been seeing on Linux CI machines for a long time now.
I think debian8-x86 was particularly susceptible to this… that could totally just be suspicion, but I guess it would be a good starting point? I’m happy to look into this on any machine on which it has been happening.
/cc @BridgeAR @Trott
The text was updated successfully, but these errors were encountered: