Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(87)

Unified Diff: tools/valgrind/valgrind_test.py

Issue 159196: Don't kill dsymutil after it finishes.... (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src/
Patch Set: Created 11 years, 5 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/valgrind/valgrind_test.py
===================================================================
--- tools/valgrind/valgrind_test.py (revision 21235)
+++ tools/valgrind/valgrind_test.py (working copy)
@@ -185,9 +185,11 @@
dsymutil_command = ['dsymutil', test_command]
- # dsymutil is crazy slow. Let it run for up to a half hour. I hope
- # that's enough.
- common.RunSubprocess(dsymutil_command, 30 * 60)
+ # dsymutil is crazy slow. Ideally we'd have a timeout here,
+ # but common.RunSubprocess' timeout is only checked
+ # after each line of output; dsymutil is silent
+ # until the end, and is then killed, which is silly.
+ common.RunSubprocess(dsymutil_command, 0)
Nico 2009/07/22 15:34:32 Uber-nit: I'd either leave out the ', 0' (it's the
if saved_test_command:
os.rename(saved_test_command, test_command)
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698