Also, the following tests are failing and need rebaseline, but I didn't see
a point in rebaselining until all the bots had cycled after commits they
depend on.
Waiting for r130080 to cycle:
fast/canvas/canvas-render-layer.html
platform/chromium/virtual/gpu/fast/canvas/canvas-render-layer.html
Waiting on r130107 to cycle:
fast/forms/week-multiple-fields/week-multiple-fields-appearance-style.html
fast/forms/week-multiple-fields/week-multiple-fields-appearance-pseudo-clas ses.html
fast/forms/week-multiple-fields/week-multiple-fields-appearance-basic.html
fast/forms/week-multiple-fields/week-multiple-fields-appearance-pseudo-elem ents.html
On Mon, Oct 1, 2012 at 5:40 PM, Ojan Vafai <o
...@chromium.org> wrote:
> Marked a bunch of flaky tests. Rolled out a couple patches. Unfortunately,
> the rollouts were spread out such that I haven't been able to to
> successfully roll.
> I've got https://codereview.chromium.org/11036017 in progress. Hopefully
> it'll stick.
> My main problem is that we only have one debug bot running the gtests and
> that bot is a Windows bot, so it takes forever. So, it wasn't until after
> my webkit roll that I noticed the gtest debug only failures (hitting an
> assert) and had to rollback.
> We should do one or both of the following:
> -Add a Linux debug bot (should cycle faster right?)
> -Add a release bot with asserts on