From 3f3c985ce49d0e605a8240f9cca57e7ea436336b Mon Sep 17 00:00:00 2001 From: Devin Nakamura Date: Tue, 24 Nov 2015 14:45:45 -0500 Subject: [PATCH] test: fix test-domain-with-abort-on-uncaught-exception.js on AIX Add SIGTRAP as an expected signal when running on AIX. Port of f45c3157 for v0.12 --- .../test-domain-with-abort-on-uncaught-exception.js | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/test/simple/test-domain-with-abort-on-uncaught-exception.js b/test/simple/test-domain-with-abort-on-uncaught-exception.js index 147540e4c3a686..6a7442ce103602 100644 --- a/test/simple/test-domain-with-abort-on-uncaught-exception.js +++ b/test/simple/test-domain-with-abort-on-uncaught-exception.js @@ -168,12 +168,16 @@ if (process.argv[2] === 'child') { // On some platforms with KSH being the default shell // (like SmartOS), when a process aborts, KSH exits with an exit // code that is greater than 256, and thus the exit code emitted - // with the 'exit' event is null and the signal is set to either - // SIGABRT or SIGILL. + // with the 'exit' event is null and the signal is set to + // SIGABRT, SIGILL, or SIGTRAP (depending on compiler). if (process.platform === 'sunos') { expectedExitCode = null; expectedSignal = ['SIGABRT', 'SIGILL']; } + if (process.platform === 'aix') { + expectedExitCode = null; + expectedSignal = ['SIGTRAP']; + } // On Windows, v8's base::OS::Abort also triggers a debug breakpoint // which makes the process exit with code -2147483645