Status: Started Owner: [email protected] Labels: Type-Bug Pri-2 OS-Mac Area-Infrastructure Size-Medium
New issue 17441 by [email protected]: tools/valgrind/chrome_test.py has bad timeout behavior when running dsymutil on mac http://code.google.com/p/chromium/issues/detail?id=17441 A developer reports: "valgrind_test.py runs dsymutil until completion (which takes 4h on my machine – I only have 2GB ram), but if dsymutil takes longer than 1800 seconds, the script then dies. It would be preferrable if dsymutil would be killed after 1800 seconds, or if there was no timeout. Letting dsymutil run until completion and then failing if it took longer than the timeout seems pointless. I will simply increase the timeout to make this work on my machine, so this is not urgent for me, just wanted to point it out." This is because tools/purify/common.py's RunSubprocess uses a blocking read, and can only check timeout between lines. It should switch to an asynchronous timeout. -- 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 -~----------~----~----~----~------~----~------~--~---
