Status: Started Owner: [email protected] Labels: Type-Bug Pri-2 OS-Linux Area-Infrastructure Size-Medium
New 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 So long, in fact, that it's timing itself out, I think. Top says: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 27430 chrome-b 20 0 1411m 1.4g 1952 R 100 37.1 8:38.99 chrome_tests.py strace says it's slowly reading in errors and parsing them. df says it's trying to chew through 700MB of XML. My favorite idea is to have valgrind not output errors we don't care about. I have a feature request in that would do that: https://bugs.kde.org/show_bug.cgi?id=201170 I'm also trying raising the timeout in chrome_tests.py temporarily. -- 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 -~----------~----~----~----~------~----~------~--~---
