On Wed, Oct 7, 2009 at 02:02, Nicolas Sylvain <[email protected]> wrote:
> Once we start tagging the flaky tests, we will monitor the flakiness > dashboard and make sure > that a test that is no longer flaky has its FLAKY_ tag removed. > It may be a good idea to expand the number of tests listed in the flakiness report from Top15 to Top20 or maybe even Top30... sometimes a test becomes only a bit less flaky, just enough to not appear in Top15. On the other hand, we have a lot of resource-related test failures (I don't know too much how Visual Studio's build system works - especially with gyp, but maybe someone will manage to investigate and fix that). This is not the fault of the test, just a bug in the build system. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
