Android One Perf bot build18-b1--device1 Having issues |
||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20One%20Perf/builds/228 https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F228%2F%2B%2Frecipes%2Fsteps%2Fdromaeo.domcoreattr_on_Android%2F0%2Fstdout DeviceUnreachableError: AG860440GACE2GC ============================================ https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F228%2F%2B%2Frecipes%2Fsteps%2Foortonline_tbmv2_on_Android%2F0%2Fstdout DeviceUnreachableError: AG860440GACE2GC ============================================ https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F228%2F%2B%2Frecipes%2Fsteps%2Fthread_times.key_idle_power_cases_on_Android%2F0%2Fstdout <<This error might mean that adb isn't seeing the device at all, so telemetry doesn't know about the browser>> Cannot find browser of type android-chromium. To list out all available browsers, rerun your command with --browser=list ============================================ https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F228%2F%2B%2Frecipes%2Fsteps%2Fv8.runtimestats.browsing_mobile_on_Android%2F0%2Fstdout Cannot find browser of type android-chromium. To list out all available browsers, rerun your command with --browser=list The next run is full of similar logs for tests running on --build18-b1--device1. Can someone from labs look at the device and see what is going on? Adding bpastene@ incase this is something swarming related.
,
Jun 27 2017
Yeah, looks like something's up with that device. The swarming logs for it have a lot of errors like "Unexpected remote ID: expected 0: WRTE, 1735, 26" which is a protocol fault in adb. Probably wouldn't hurt to reflash the device.
,
Jun 28 2017
,
Jun 28 2017
Device AG860440GACE2GC has been reflashed.
,
Mar 30 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bpastene@chromium.org
, Jun 27 2017