Device offline on chromium.perf Android Nexus9 Perf (2) |
||||
Issue descriptionLink to buildbot status page: https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/3243 Device HT4B6JT02450 blacklisted
,
Sep 28 2016
HT4B6JT02450 blacklist reason: it was unauthorized checked the keys, it was missing the infra key so added that onto the device. List of devices attached HT4B7JT01243 device HT4B7JT01981 device HT4B7JT01232 device HT4B6JT02657 device HT4B7JT01059 device HT4B7JT01277 device HT4B6JT02450 device
,
Sep 29 2016
HT4B6JT02450 still lists "adb status unauthorized": https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/3248
,
Sep 29 2016
This one was weird. I ack'd the usb auth. debugging prompt. Reconnect the usb cable and was challenged with the prompt again. I blew away the adb_keys file and let it recreate a new one, but still the same behavior. So I re-flashed it and now verification sticks. Effective starting with https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus9%20Perf%20%282%29/builds/3250 List of devices attached HT4B6JT02450 device HT4B7JT01981 device HT4B7JT01059 device HT4B7JT01277 device HT4B6JT02657 device HT4B7JT01243 device HT4B7JT01232 device
,
Sep 29 2016
Thanks Peter! Annie, let us know if re-flashing didn't do the trick. |
||||
►
Sign in to add a comment |
||||
Comment 1 by jo...@google.com
, Sep 28 2016Status: Assigned (was: Untriaged)