GTTF: prevent a browser_tests timeout from looking like a success.
BUG=57578
TEST=none
Review URL: http://codereview.chromium.org/3575012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61488 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/test/in_process_browser_test.cc b/chrome/test/in_process_browser_test.cc
index 08959504..75740ae7 100644
--- a/chrome/test/in_process_browser_test.cc
+++ b/chrome/test/in_process_browser_test.cc
@@ -287,6 +287,13 @@
}
void InProcessBrowserTest::RunTestOnMainThreadLoop() {
+#if defined(OS_POSIX)
+ // Restore default signal handler for SIGTERM, so when the out-of-process
+ // test runner tries to terminate us, we don't catch it and possibly make it
+ // look like a success (http://crbug.com/57578).
+ signal(SIGTERM, SIG_DFL);
+#endif // defined(OS_POSIX)
+
// On Mac, without the following autorelease pool, code which is directly
// executed (as opposed to executed inside a message loop) would autorelease
// objects into a higher-level pool. This pool is not recycled in-sync with
