Can someone from infra-labs take a look? Looks like device authorization failed: https://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/622

(Can't find the device id but there should only be one device attached to build43-b4)

This looks like it was a flake?  The device does authorize.  Repeating the step that failed:

chrome-bot@build43-b4:/b/build/slave/android_s5_perf_bisect/build$ python -u /b/build/scripts/slave/android/authorize_adb_devices.py --verbose --adb-path /b/build/slave/android_s5_perf_bisect/build/src/third_party/android_tools/sdk/platform-tools/adb
DEBUG:root:/b/build/slave/android_s5_perf_bisect/build/src/third_party/android_tools/sdk/platform-tools/adb kill-server
DEBUG:root:/b/build/slave/android_s5_perf_bisect/build/src/third_party/android_tools/sdk/platform-tools/adb devices
DEBUG:root:Unauthorized devices: []
DEBUG:root:/b/build/slave/android_s5_perf_bisect/build/src/third_party/android_tools/sdk/platform-tools/adb kill-server

./adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3208582597be5193	device