[chromium-dev] Re: Tree flakyness

2008-12-18 Thread Scott Violet
I've filed bugs to track these (minus the ones Ojan fixed): > 122 BrowserTest.JavascriptAlertActivatesTab 5668 > 82 ErrorPageTest.DNSError 5669 > 52 BrowserTest.TabNavigationAccelerators 5670 > 35 ChromeMainTest.SecondLaunch 5671 > 35 AutomationProxyTest.GetTa

[chromium-dev] Re: Tree flakyness

2008-12-16 Thread Søren Gjesse
Regarding PERF TESTS I have committed a change which drops the use of for WebCore::ConsoleMessage::operator== for now. Lets see how the tests reacts to this. /Søren On Tue, Dec 16, 2008 at 1:58 AM, Nicolas Sylvain wrote: > Hello, > As you all know, our tests are really flaky and are causing the

[chromium-dev] Re: Tree flakyness

2008-12-16 Thread John Abd-El-Malek
On Mon, Dec 15, 2008 at 4:58 PM, Nicolas Sylvain wrote: > Hello, > As you all know, our tests are really flaky and are causing the tree to be > red too often. > I took a quick look at the test logs and compiled the stats about all the > flakyness. > > UI TESTS: > In the last 7 days, 188 ui te

[chromium-dev] Re: Tree flakyness

2008-12-15 Thread Ojan Vafai
I have a fix pending for the CrossSite* ones. On Mon, Dec 15, 2008 at 4:58 PM, Nicolas Sylvain wrote: > Hello, > As you all know, our tests are really flaky and are causing the tree to > be red too often. > > I took a quick look at the test logs and compiled the stats about all the > flakynes