Comment #3 on issue 18738 by [email protected]: MetricsService.CrashRenderers is flaky http://code.google.com/p/chromium/issues/detail?id=18738
...pkastig may not like hearing the answer... but... Given huanr's comment, it sounds like there is a race between the navigation to about:crash (which should crash the renderer) and the test completing and deciding that the render hasn't (yet) crashed. It may well be that darin's sleep is not long enough on the current testing boxes and setups. Have we considered upping the sleep to several seconds?? It wouldn't be pretty... but if I understand the problem, it is the correct way to go. This test will always be flaky (since the render may pause for an arbitrary length of time before navigating), but adjusting the sleep should be able to significantly reduce the likelihood of a false alarm. -- 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 -~----------~----~----~----~------~----~------~--~---
