You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to set up tests running llnode against coredumps. I've noticed that the current suite only tests attaching to a running process, and I'd like to extend it to run the same tests on an aborted process (I think the simplest method would be to run with --abort-on-uncaught-exception and then run the existing suite on the dump).
Does anyone have any views on how this should look (or how this should be implemented)?
Testing on TravisCI is working, and the Build WG is working to create a llnode job on Jenkins (nodejs/build#1025). Since we have a llnode test suite working right now and there's a tracking issue to create the Jenkins job, I'll close this, but feel free to reopen.
Activity
rnchamberlain commentedon Oct 17, 2016
+1 for this, I would suggest testing core dumps from segv crash and out of memory scenarios as well as uncaught exception.
indutny commentedon Oct 18, 2016
Sounds interesting indeed!
It'll most likely require a custom CI infrastructure with the core dumps enabled. cc @nodejs/jenkins-admins and @thealphanerd maybe?
indutny commentedon Nov 23, 2016
We have one test case that checks core dumps on OS X at the moment. It would be great to have something broader for other unixes too.
bnoordhuis commentedon Jun 21, 2017
@gibfahn Are you still working on this?
gibfahn commentedon Jun 30, 2017
First step is getting tests in CI with nodejs/build#777.
mmarchini commentedon Jun 6, 2018
Testing on TravisCI is working, and the Build WG is working to create a llnode job on Jenkins (nodejs/build#1025). Since we have a llnode test suite working right now and there's a tracking issue to create the Jenkins job, I'll close this, but feel free to reopen.