Skip to content
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

Closed
addaleax opened this issue Apr 3, 2018 · 10 comments
Closed

Requesting access to debian8-x86 for debugging spooky failures #1207

addaleax opened this issue Apr 3, 2018 · 10 comments

Comments

@addaleax
Copy link
Member

addaleax commented Apr 3, 2018

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

@gibfahn
Copy link
Member

gibfahn commented Apr 3, 2018

SGTM

@Trott
Copy link
Member

Trott commented Apr 3, 2018

This is definitely happening on debian8-x86 often. Here is a overview of most reports:

@BridgeAR Alas, those are all now 404s....

@Trott
Copy link
Member

Trott commented Apr 3, 2018

SGTM

@Trott
Copy link
Member

Trott commented Apr 3, 2018

(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.)

@mhdawson
Copy link
Member

mhdawson commented Apr 3, 2018

SGTM

@addaleax
Copy link
Member Author

addaleax commented Apr 6, 2018

@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

@rvagg
Copy link
Member

rvagg commented Apr 6, 2018

@addaleax root@169.44.16.126, all yours, just ping nodejs/build here when you're done so someone can clean up, or you're welcome to remove your keys from .ssh/authorized_keys when you don't think you need it anymore.

@addaleax
Copy link
Member Author

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 ~iojs/debug-18998/ – it’s 1.6 GB of debugging stuff. :)

@addaleax
Copy link
Member Author

Okay, I’ve removed my own access now. Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants