New issue
Advanced search Search tips

Issue 753685 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

provision_devices failing on chromium.webkit/WebKit Android (Nexus4)

Project Member Reported by shimazu@chromium.org, Aug 9 2017

Issue description

provision_devices failing on chromium.webkit/WebKit Android (Nexus4)

Builders failed on: 
- WebKit Android (Nexus4): 
  https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29

Troopers: could you take a look at this issue?

 
Cc: bpastene@chromium.org
Status: WontFix (was: Available)
THis has since been resolved, i don't know how. 
maybe +bpastene@ ? :)
Status: Untriaged (was: WontFix)
Failing again now.
Components: -Infra Infra>Client>Android Infra>Client>Chrome
Labels: OS-Android Type-Bug
Owner: jbudorick@chromium.org
Status: Started (was: Untriaged)
This is device_recovery failing and letting provision_devices take the blame again.

This happens pretty infrequently, so I'm downgrading it to P2. Looking at it now, though.
Status: WontFix (was: Started)
Looks green all day today. 2 devices are healthy and one is missing though.
Status: Assigned (was: WontFix)
Well, right after that it had two purple builds:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/68568
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/68567

but now it recovered. Still needs something to happen though - add more devices?
I doubt we have too many N4s laying around...

Comment 7 by pschm...@google.com, Aug 21 2017

We have about a dozen spare N4's.   Assign this to me if you want any added.

Comment 8 by tapted@chromium.org, Aug 22 2017

Labels: -Sheriff-Chromium
popping off the sheriff queue, things seem mostly stable in https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29?numbuilds=200 land, but there was a failure ~1 hour ago, and a batch of 4 failures ~10 hours ago.
Labels: -Pri-1 Pri-2
Project Member

Comment 10 by bugdroid1@chromium.org, Sep 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ecabf7c2cca920ac123c2f0df3075026a8103069

commit ecabf7c2cca920ac123c2f0df3075026a8103069
Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org>
Date: Fri Sep 22 03:48:18 2017

Roll src/third_party/catapult/ 33d54da00..703485470 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/33d54da00a77..703485470a88

$ git log 33d54da00..703485470 --date=short --no-merges --format='%ad %ae %s'
2017-09-21 jbudorick [devil] Explicitly start the adb server in recovery after killing it.

Created with:
  roll-dep src/third_party/catapult
BUG= 753685 


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: Ia5697160374e954b19638c381c115c4ac2fc66e8
Reviewed-on: https://chromium-review.googlesource.com/677861
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#503643}
[modify] https://crrev.com/ecabf7c2cca920ac123c2f0df3075026a8103069/DEPS

Status: Fixed (was: Assigned)
I think this should be fixed now and am tentatively marking it as such. I'll try to check in on the bot occasionally, but if you see a recurrence here, please don't hesitate to reopen it.

Sign in to add a comment