From 1809845d5a97f75add9e62cfb6df158fbbb2ca5e Mon Sep 17 00:00:00 2001 From: "thestig@chromium.org" Date: Tue, 17 Sep 2013 20:05:25 +0000 Subject: Valgrind/Heapcheck: Do not try to run layout tests with 0 jobs. NOTRY=true Review URL: https://chromiumcodereview.appspot.com/23868039 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@223662 0039d316-1c4b-4281-b951-d872f2087c98 --- tools/heapcheck/chrome_tests.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools/heapcheck') diff --git a/tools/heapcheck/chrome_tests.py b/tools/heapcheck/chrome_tests.py index d5ba2e94..444df8e 100755 --- a/tools/heapcheck/chrome_tests.py +++ b/tools/heapcheck/chrome_tests.py @@ -379,7 +379,7 @@ class ChromeTests(object): # While Heapcheck is not memory bound like Valgrind for running layout tests # in parallel, it is still CPU bound. Many machines have hyper-threading # turned on, so the real number of cores is actually half. - jobs = int(multiprocessing.cpu_count() * 0.5) + jobs = max(1, int(multiprocessing.cpu_count() * 0.5)) script_cmd = ["python", script, "-v", "--run-singly", # run a separate DumpRenderTree for each test "--fully-parallel", -- cgit v1.1