tools,test: show signal code when test crashes#7859
tools,test: show signal code when test crashes#7859santigimeno merged 1 commit intonodejs:masterfrom
Conversation
tools/test.py
Outdated
There was a problem hiding this comment.
Perhaps it might be helpful to add a prefix before the number here and below, like "Exit code ".
There was a problem hiding this comment.
Would --- CRASHED (Signal: %d) --- work for you?
|
PR updated. Thanks! |
|
LGTM but does it print the right thing on Windows? |
@bnoordhuis I don't know. Is there a simple way to force a crash on |
|
PR update adding |
|
@santigimeno I normally use |
|
@gibfahn I didn't know about |
|
PR updated printing the Signal Code on every platform but |
tools/test.py
Outdated
There was a problem hiding this comment.
I'd negate in PrintCrashed() itself.
|
LGTM with a suggestion and a style nit. |
|
PR updated with @bnoordhuis comments. Thanks! |
On every platform but `Windows`. Also, print the crash information when using the tap reporter. PR-URL: nodejs#7859 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
|
Landed in df4ef63. Thanks! |
On every platform but `Windows`. Also, print the crash information when using the tap reporter. PR-URL: #7859 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
On every platform but `Windows`. Also, print the crash information when using the tap reporter. PR-URL: #7859 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
On every platform but `Windows`. Also, print the crash information when using the tap reporter. PR-URL: #7859 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
On every platform but `Windows`. Also, print the crash information when using the tap reporter. PR-URL: #7859 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Checklist
make -j4 test(UNIX), orvcbuild test nosign(Windows) passesAffected core subsystem(s)
tools, test
Description of change