Android WebView N (dbg) having trouble with provisioning of devices |
||||||||
Issue description
Alert Details
------------------
Too many consecutive infra failures on master.chromium.android:Android WebView N (dbg).
name: ConsecutiveInfraFailures
current value: 1
threshold: VAL > 0 for 10m
alert fields: {, metric:escaped_builder=Android%20WebView%20N%20(dbg),metric:short_master=chromium.android,metric:builder=Android WebView N (dbg),metric:master=master.chromium.android}
Looking at https://build.chromium.org/p/chromium.android/builders/Android%20WebView%20N%20%28dbg%29 the last 20 builds have had 3 infra failures. The failing builds all get an exception in the provision_devices step:
"
I 0.005s TimeoutThread-1-for-MainThread [host]> /b/c/b/Android_WebView_N__dbg_/src/third_party/android_tools/sdk/platform-tools/adb devices
step returned non-zero exit code: 87
@@@STEP_EXCEPTION@@@
"
,
Dec 16 2016
Assigned to bpastene since I think he might know the most about provisioning the android devices. Feel free to reassign if appropriate.
,
Dec 16 2016
,
Dec 17 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/dfa7fcd3449daed39bbbf490294364446d728c9c commit dfa7fcd3449daed39bbbf490294364446d728c9c Author: catapult-deps-roller <catapult-deps-roller@chromium.org> Date: Sat Dec 17 06:35:11 2016 Roll src/third_party/catapult/ 42ba4dfff..4fc181694 (4 commits). https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/42ba4dfff160..4fc181694898 $ git log 42ba4dfff..4fc181694 --date=short --no-merges --format='%ad %ae %s' 2016-12-16 dtu [pinpoint] Move Quests to their own modules. 2016-12-16 ssid Remove enable-memory-benchmarking flag from unittest 2016-12-16 bpastene devil: Make provision_devices.py complain when no devices are available. 2016-12-16 simonhatch Dashboard - Set recipe_tester_name on staging bots. BUG= 513692 , 674473 ,672524 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=catapult-sheriff@chromium.org Review-Url: https://codereview.chromium.org/2581703004 Cr-Commit-Position: refs/heads/master@{#439331} [modify] https://crrev.com/dfa7fcd3449daed39bbbf490294364446d728c9c/DEPS
,
Jan 6 2017
,
Jan 19 2017
@bpastene - is this still an issue? Or even something that infra should be on the hook for?
,
Jan 19 2017
re your second question: device provisioning is something we own.
,
Jan 19 2017
Looks like it still randomly fails because it's only device is offline. There's not much we can do to prevent that. I'll work on adding a 2nd device.
,
Jan 19 2017
,
Jan 20 2017
Could we add monitoring/alerting for devices going offline?
,
Jan 20 2017
#10: we already have monitoring for devices; see the device_monitor steps on each build. These bubble up as tickets sent to g/cit-android.
,
Jan 25 2017
,
Feb 10 2017
,
Dec 4 2017
Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android
,
Dec 4 2017
,
May 25 2018
Old issue. Bot seems fine now: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Android%20WebView%20N%20%28dbg%29 |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by katthomas@google.com
, Dec 16 2016Labels: -Pri-2 Infra-Failures OS-Android Pri-1
Owner: bpastene@chromium.org
Status: Assigned (was: Untriaged)