I agree that the chromium buildbot seems to have more flakiness on layout tests that webkit buildbots. Here's two things that may help us to understand this: 1. It would be nice to save crash logs from OSX into the zip file. For example, this run
http://build.chromium.org/buildbot/waterfall/builders/Webkit%20Mac10.5%20(dbg)(2)/builds/3323/steps/webkit_tests/logs/stdio had a crash and likely generated a crash log at ~/Library/Logs/CrashReporter/TestShell*.crash which would help point to a culprit. 2. If we suspect that tests may pass if given more time, then increase the timeout and see if more tests pass but exceed this old timeout (log something when this happens so we can validate that it is working). Dave On Tue, Sep 8, 2009 at 5:41 PM, Dirk Pranke <[email protected]> wrote: > > From what I've poked around at, many of the LayoutTest flaky failures > are timeout-related. There's something in the test harness and web > server configurations that cause tests to be unpredictably slower. I > don't think Apple has this problem, and I think that's because they > use the built in apache instance in OS X, and also because they have a > very different model for test execution (how we run tests in > parallel). This is pure speculation, though, and I'm sure some of the > more senior people on the team can correct me or add more. > > -- Dirk > > > On Tue, Sep 8, 2009 at 5:14 PM, Pawel Hajdan<[email protected]> wrote: > > I'm trying to understand why some layout tests are flaky. Does WebKit > have > > the same problem? When I visit build.webkit.org something is always red, > so > > it may be flakiness. > > What are the most common causes of layout tests failures for Chromium? > Flaky > > crashes seem to be especially weird. > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
