I'll take the bug for now to identify the WebKit rev that caused the
regression.
On Wed, Jan 6, 2010 at 20:10, Robert Sesek <rse...@chromium.org> wrote:
> Good evening,
>
> At 9pm ET, the tree was significantly red and Erik Kay closed the tree: Win
> browser_tests, Win & Mac perf, Linux views, and Win Webkit all were red. I
> cleaned up the Win browser_tests, Linux Views, and Win WebKit redness, but
> the Win & Mac perf regressions are still in play. mpcompete, jamesr, and I
> debated about what to do with this since it originated from a fairly
> significant WebKit roll:
> http://src.chromium.org/viewvc/chrome?view=rev&revision=35646. Backing out
> didn't seem like the best option because it was large jump and another roll
> happened later at r35669. The tree *is still closed* as of 11pm ET because
> http://crbug.com/31698 (tracking bug for this perf regression) does not
> yet have an owner and it desperately needs one! If in the morning someone
> more knowledgeable feels like we can open, please do.
>
> Also, I didn't have time to track it down tonight, but Windows UI
> Interactive (dbg) has been red on and off for the past couple of cycles,
> starting at
> http://build.chromium.org/buildbot/waterfall/builders/Interactive%20Tests%20(dbg)/builds/19501.
> I'm hesitant to mark it as flaky without knowing a little more, but I backed
> out oshima's change (the likely candidate) and the redness continued. Help
> appreciated :).
>
> Thanks and good night!
>
> rsesek / @chromium.org
>
> --
> Chromium Developers mailing list: chromium-dev@googlegroups.com
> View archives, change email options, or unsubscribe:
> http://groups.google.com/group/chromium-dev
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
