Comment #1 on issue 17484 by [email protected]: chrome_tests.py is
taking too long to analyze log files
http://code.google.com/p/chromium/issues/detail?id=17484
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=21365
------------------------------------------------------------------------
r21365 | [email protected] | 2009-07-22 18:30:20 -0700 (Wed, 22 Jul 2009) |
6 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/build-valgrind-for-chromium.sh?r1=21365&r2=21364
A
http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/possible.patch
Add new option --show-possible to valgrind for later use by
valgrind_test.py to speed up log processing.
BUG=17484
TEST=run to install new valgrind; sh tools/valgrind/chrome_tests.sh -t base
--tool_flags="--nocleanup_on_exit --show-possible=no"; grep PossiblyLost
valgrind.tmp/* should find no matches.
Review URL: http://codereview.chromium.org/159251
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
