Comment #2 on issue 24708 by [email protected]: Hidden Flakiness in BrowserEncodingTest.TestOverrideEncoding (others?) http://code.google.com/p/chromium/issues/detail?id=24708
I tried it again on my machine and can still reproduce it in debug build, manually called from the command line (doing Cursor- Up - Enter repeatedly with --gtest_filter=BrowserEncodingTest.TestOverrideEncoding) in CygWin. Can't reproduce it from the debugger, though - perhaps that's too slow (cf. below). There seems to be a racing condition if the test shell shuts down immediately after WaitForNavigation. I.e., step 1.) in my list (remove the remaining code after WaitForNavigation) is necessary, otherwise what comes after will take enough time to mask the issue. After more debugging I'm also not sure that the pipe error is what leads to the failure, it could just be that the leak detector fires before everything has shut down. I therefore added a line to my test that explicitely closes the tab before finishing the test, that got rid of the flakiness. All said, I don't think it's a terribly bad bug... -- 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 -~----------~----~----~----~------~----~------~--~---
