On Tue, Oct 27, 2009 at 11:37 PM, Paweł Hajdan Jr. <[email protected]>wrote:
> On Wed, Oct 28, 2009 at 00:44, Ian Fette <[email protected]> wrote: > >> In an effort to provide more transparency into what the team is working >> on, I'm sending out the meeting notes from the green tree task force to >> chromium-dev, below. I will try to send further notes to chromium-dev from >> our meetings. >> > > Sounds great! > > >> >> - Flakiness >> - Brought down to acceptable levels for unit tests. Need help to >> keep it that way and not regress. >> >> I think that unit_tests are well and happy, but ui_tests are another > story. We have UI tests which have more than 100 flaky flips in just two > weeks. And we have UI tests which fail on almost every try run. IMHO such > "outstanding" (is that the right word?) cases of flakiness should be fixed > with a high enough priority. > A bunch of these are related to DOM Storage. I'm pretty sure the cause is related to what's causing a lot of crashes in the dev channel. I'm working actively to figure it out....even though it has been this way for a while now. > And we still have lots of problems with resource-related flakiness, like > this: > > [FATAL:resource_bundle.cc(133)] Check failed: false. > > [FATAL:tab_renderer.cc(132)] Check failed: waiting_animation_frames->width() > % waiting_animation_frames->height() == 0. > > This is making all ui tests super-flaky. It's windows-specific, and I was > asking about the issue several times on chromium-dev. Unfortunately, I don't > know how to fix or even analyse it (but I can help). Please note that fixing > this should visibly decrease flakiness of all ui tests, not only the Top25 > flaky ones. > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
