New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 604655 link

Starred by 1 user
Status: Fixed
Owner:
█ mikec...@chromium.org
Last visit > 30 days ago
Closed: Apr 2016
Cc:
perezju@chromium.org
█ mikec...@chromium.org
█ torbjorng@chromium.org
solenberg@chromium.org
█ deadbeef@chromium.org
jbudorick@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

content_browsertests failing on Android device testers

Project Member Reported by kjellander@chromium.org, Apr 19 2016 
Around 5-6pm Apr 18, content_browsertests started failing on several Android device testers:

chromium.android waterfall:
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester/builds/4168
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Low-end%20Tester/builds/3056
https://build.chromium.org/p/chromium.android/builders/Lollipop%20Tablet%20Tester/builds/2776
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit%20Tester/builds/1537
https://build.chromium.org/p/chromium.android/builders/Marshmallow%20Tablet%20Tester/builds/3618

chromium.webrtc.fyi waterfall:
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Android%20Tests%20%28dbg%29%20%28L%20Nexus9%29/builds/11081
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Android%20Tests%20%28dbg%29%20%28L%20Nexus7.2%29/builds/11127
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Android%20Tests%20%28dbg%29%20%28L%20Nexus6%29/builds/5688
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Android%20Tests%20%28dbg%29%20%28L%20Nexus5%29/builds/11068

The test normally takes about 5 minutes to run, but now it is killed after 46 minutes on all the above bots.

By comparing multiple builds, I tracked down these Chromium changes:
https://chromium.googlesource.com/chromium/src/+log/97c4403e..8ed6849

and these infra changes:
https://chromium.googlesource.com/chromium/tools/build.git/+log/08b75ce3..36797f99
but I'm unable to find a culprit yet.

I'm suspecting https://codereview.chromium.org/1844843002 though.

Comment 1 by kjellander@chromium.org, Apr 19 2016

Cc: mikec...@chromium.org
Labels: -Pri-3 Pri-1
I'm going to try to repro locally

Comment 2 by jbudorick@chromium.org, Apr 19 2016

Cc: perezju@chromium.org
+perezju, current emea android sheriff

Comment 3 by bpastene@chromium.org, Apr 19 2016

Labels: -Infra Infra-Android

Comment 4 by kjellander@chromium.org, Apr 19 2016 

I tried repro locally and the content browser test executable crashed on the device with an "OK" prompt. However reverting https://codereview.chromium.org/1844843002 locally gave me compile errors and I don't have more time to look into this now.

I also can't explain why this doesn't hit the regular Android testers in chromium.linux waterfall.

Comment 5 by jbudorick@chromium.org, Apr 19 2016 

#4: at a glance, probably L+, given that these failures don't appear on https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Tester

Comment 6 by solenberg@chromium.org, Apr 19 2016

Cc: deadbeef@chromium.org

Comment 7 by stip@chromium.org, Apr 19 2016 

When we move these to swarming we'll be able to have stricter lockdown on step timeouts, as in https://chromium.googlesource.com/chromium/src/+/b5f475b530a82f9d4dc9e10d709ef2a980e71241/testing/buildbot/chromium.linux.json#157.

Comment 8 by jbudorick@chromium.org, Apr 20 2016

Owner: mikec...@chromium.org
Status: Fixed (was: Untriaged)
I think this was resolved by https://codereview.chromium.org/1898353002

Comment 9 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>Android
Labels: -Infra-Android
►

Sign in to add a comment