summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrnk@chromium.org <rnk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-02-21 21:40:32 +0000
committerrnk@chromium.org <rnk@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-02-21 21:40:32 +0000
commit4d805b5db89c08532633e9fcacdc4df0828fe1fe (patch)
treea75552b2b1f23cb8f0b89f9c2a1eac998947a454
parent5b023e75e72b0f2c26eaae19764b8db7763eccaa (diff)
downloadchromium_src-4d805b5db89c08532633e9fcacdc4df0828fe1fe.zip
chromium_src-4d805b5db89c08532633e9fcacdc4df0828fe1fe.tar.gz
chromium_src-4d805b5db89c08532633e9fcacdc4df0828fe1fe.tar.bz2
Try to fix webkit memcheck bot timeouts with --no-show-results
I noticed that firefox was hanging around after the tests were done running. That might be causing problems with shutting down. TBR=timurrrr@chromium.org BUG=176908 Review URL: https://codereview.chromium.org/12340011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@183864 0039d316-1c4b-4281-b951-d872f2087c98
-rwxr-xr-xtools/valgrind/chrome_tests.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/tools/valgrind/chrome_tests.py b/tools/valgrind/chrome_tests.py
index d096979..676508a 100755
--- a/tools/valgrind/chrome_tests.py
+++ b/tools/valgrind/chrome_tests.py
@@ -425,6 +425,8 @@ class ChromeTests:
"--fully-parallel",
"--time-out-ms=200000",
"--no-retry-failures", # retrying takes too much time
+ # http://crbug.com/176908: Don't launch a browser when done.
+ "--no-show-results",
"--nocheck-sys-deps"]
# Pass build mode to run_webkit_tests.py. We aren't passed it directly,
# so parse it out of build_dir. run_webkit_tests.py can only handle