Tree status, end of pkasting sheriff stint

[Peter Kasting]

(+CC everyone mentioned by name in this mail)

It's the end of my 4 days of sheriffing.  I've just updated Chromium's DEPS to WebKit r146842, which is fairly close to ToT, and should be OK (fingers crossed) other than some layout test redness.

The tree 's current issues:

* The Android Chromium test bot ( http://build.chromium.org/p/chromium.webkit/builders/Android%20Tests%20%28dbg%29 ) has redness I never investigated, because I got so used to seeing that bot red, that I didn't realize it had gone green and back to red until just now.  Oops.

* The Win7 Perf bot ( http://build.chromium.org/p/chromium.webkit/builders/Win7%20Perf )  startup_test is timing out, which is the same failure I mailed Marcus about several days ago, but never heard anything on.

* Both Win7 and Mac 10.6 ( https://code.google.com/p/chromium/issues/detail?id=223521 ) Perf bots are crashing on dromao_domcoremodify, which is https://code.google.com/p/chromium/issues/detail?id=223521 .  The most likely candidate for this looked to me like http://trac.webkit.org/changeset/146672 , which is from Dane, r+=Ryosuke.  Could the two of you investigate whether that change is at fault here?

* The Layout Test canaries have various redness which I believe is pretty much all fallout from a change James made earlier tonight.  He's been rebaselining things, so I'm not worried about this.

PK

[Marcus Bulach]

On Tue, Mar 26, 2013 at 4:20 AM, Peter Kasting <pkas...@chromium.org> wrote:

(+CC everyone mentioned by name in this mail)

It's the end of my 4 days of sheriffing.  I've just updated Chromium's DEPS to WebKit r146842, which is fairly close to ToT, and should be OK (fingers crossed) other than some layout test redness.

The tree 's current issues:

* The Android Chromium test bot ( http://build.chromium.org/p/chromium.webkit/builders/Android%20Tests%20%28dbg%29 ) has redness I never investigated, because I got so used to seeing that bot red, that I didn't realize it had gone green and back to red until just now.  Oops.

The android devices unfortunately have all sorts of issues with keeping up with the usb connection. A bunch of people are working on making them more reliable, but for the time being, if they go "offline" or "missing device", please file a bug to chrome-infrastructure-bugs@, assign to sivac...@chromium.org and he'll take care of it, similarly to:

https://code.google.com/p/chromium/issues/detail?id=223575

 

* The Win7 Perf bot ( http://build.chromium.org/p/chromium.webkit/builders/Win7%20Perf )  startup_test is timing out, which is the same failure I mailed Marcus about several days ago, but never heard anything on.

Sorry, my bad.

A few tests are failing / hanging without producing any output whatsoever, which doesn't help triaging. I filed these bugs in order to improve the output and get better information.

https://code.google.com/p/chromium/issues/detail?id=223117

https://code.google.com/p/chromium/issues/detail?id=223572

I was expecting to get those in order to investigate the startup_test, as it's not printing any information whatsoever. I apologize for not doing that.

I filed a bug specifically for this test:

https://code.google.com/p/chromium/issues/detail?id=223894