Status: Untriaged Owner: [email protected] Labels: Type-Bug Pri-2 OS-All Area-Infrastructure Size-Medium
New issue 10501 by [email protected]: AutomationProxy::GetLastActiveBrowserWindow seems to be flakey http://code.google.com/p/chromium/issues/detail?id=10501 When I was testing one of my changes, which was eventually submitted as r13312, the try server always reported failure for the UI test I added. But I could run the test successfully on local machine. I found out the test failed on try server because automation()- > GetLastActiveBrowserWindow() returns invalid handle. I worked around the issue by changing to automation()->GetBrowserWindow(0), which turns out to be reliable. We need to fix GetLastActiveBrowserWindow() but it is difficult to repro. In the mean time, I will change a few places that use GetLastActiveBrowserWindow(). -- 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 -~----------~----~----~----~------~----~------~--~---
