Comment #2 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=21374
------------------------------------------------------------------------
r21374 | [email protected] | 2009-07-22 21:22:18 -0700 (Wed, 22 Jul 2009) |
7 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/valgrind_test.py?r1=21374&r2=21373
Part 2 of secret plan to speed up valgrind log processing.
Commit after previous change to build-valgrind-for-chromium.sh is committed
and run.
BUG=17484
TEST=sh tools/valgrind/chrome_tests.sh -t base
--tool_flags="--nocleanup_on_exit"; grep PossiblyLost valgrind.tmp/* should
find no matches.
Review URL: http://codereview.chromium.org/159252
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
