GeezerVison

CI: https://ci.nodejs.org/job/node-test-pull-request/12044/

I still haven't figured out how to drill through Jenkins to find the console output for the CI failure.

I still haven't figured out how to drill through Jenkins to find the console output for the CI failure.

@davisjam In this case:

• go to the bottom center of the CI page and follow the link that says build #14753 (to the right of node-test-commit)
• scroll to the bottom of the resulting page and find the one that failed (with a white exclamation point inside a red circle), in this case node-test-commit-plinux. Follow the link to the right of it that says build #13879
• once again, on the resulting page, scroll to the bottom and look at the bottom center to find the host that failed (again, denoted by an exclamation point). In this case, it's ppcle-ubuntu1404. Follow that link.
• On the resulting page, you now have two options. For a nifty readable interface, select "Console Output" from the list of links on the left side. There's also a plain text option "View as plain text" under that "Console Output" link. In this particular case, it looks like the build failed during the compilation of addons or something like that. No tests were run. Or something weird happened anyway:

make: *** [run-ci] Error 2
Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information

@nodejs/build FYI on that build failure (for anyone that wants to investigate mysterious build failures, no need to comment here, although feel free to open an issue in nodejs/build or wherever of course!).

Just in case it really is a problem with this PR (which seems highly unlikely), here's a re-run:
https://ci.nodejs.org/job/node-test-commit-plinux/13885/

@davisjam If the instructions for getting to the console output above don't work for you, let me know what step you got stuck on and I'll try to provide a screenshot or something.

Thanks a lot. Landed in dd2200e

@davisjam please note that the commit message was not according to the commit guidlines that are linked in the the PR. I added the subsystem accordingly.

@BridgeAR Thank you for fixing that. I'll try to be more careful.

@Trott Thanks for the guide. I see the failure now. Definitely not my fault :-)