Avi, thanks! We should also keep an eye on the cycle times for the bots to see how much more time they take with the pixel tests enabled.
TVL On Fri, Oct 2, 2009 at 11:55 AM, Avi Drissman <a...@google.com> wrote: > That didn't turn out so bad. Pixel tests turned on as of r27839. The first > batch had failures > > > http://build.chromium.org/buildbot/waterfall/builders/Webkit%20Mac10.5/builds/4417/steps/webkit_tests/logs/stdio > > but the second one had just a timeout: > > > http://build.chromium.org/buildbot/waterfall/builders/Webkit%20Mac10.5%20%28dbg%29%281%29/builds/4845/steps/webkit_tests/logs/stdio > > I think that'll do it. Let's let this run for a few cycles and throw flaky > tests into the expectations. > > Avi > > > > On Fri, Oct 2, 2009 at 9:52 AM, Avi Drissman <a...@google.com> wrote: > >> I'm turning on the Mac pixel tests today. There's two parts to this. First >> is the new expectations (http://codereview.chromium.org/249043) which >> just adds IMAGE failures and won't affect anything. The second is telling >> the bots to run the pixel tests (http://codereview.chromium.org/242099) >> and that might be an issue. If everything goes as planned, no one will >> notice. If things do not go as planned, the first build after the second >> checkin might fail with pixel issues. If that happens, blame me. >> >> Avi >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
