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

Issue 159196: Don't kill dsymutil after it finishes.... (Closed)

Created:
11 years, 5 months ago by dank
Modified:
9 years, 7 months ago
Reviewers:
Nico
CC:
chromium-reviews_googlegroups.com, not_the_right_glider, stuartmorgan, dank, the_wrong_timurrrr, Nirnimesh
Visibility:
Public.

Description

Don't kill dsymutil after it finishes. BUG=17441 TEST=sh tools/valgrind/chrome_test.sh -t ui on mac, watch it not time out when running dsymutil Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=21361

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+5 lines, -3 lines) Patch
M tools/valgrind/valgrind_test.py View 1 chunk +5 lines, -3 lines 1 comment Download

Messages

Total messages: 2 (0 generated)
dank
Is this the workaround you used?
11 years, 5 months ago (2009-07-22 15:17:26 UTC) #1
Nico
11 years, 5 months ago (2009-07-22 15:34:32 UTC) #2
LGTM.

It's the workaround I'm going to use tonight, yes.

http://codereview.chromium.org/159196/diff/1/2
File tools/valgrind/valgrind_test.py (right):

http://codereview.chromium.org/159196/diff/1/2#newcode192
Line 192: common.RunSubprocess(dsymutil_command, 0)
Uber-nit: I'd either leave out the ', 0' (it's the default) or put a '# 0 means
no timeout' somewhere.

Powered by Google App Engine
This is Rietveld 408576698