This looks the same as https://bugs.chromium.org/p/chromium/issues/detail?id=713747#c3

The device has set sys.boot_completed but it hasn't finished booting?

+jbudorick

https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Ftryserver.chromium.perf%2Fandroid_webview_arm64_aosp_perf_bisect%2F1080%2F%2B%2Frecipes%2Fsteps%2Fprovision_devices%2F0%2Fstdout

Same root cause as 713883. Should get a chance to address that soon.

Looks like a single device builder with a borked device?

C   99.411s ProvisionDevice(020232abc2931127)  (TimeoutThread-3-for-ProvisionDevice(020232abc2931127)) Exception on EnableRoot(020232abc2931127, retries=3, timeout=30), attempt 3 of 4: DeviceUnreachableError('020232abc2931127',)
I   99.411s TimeoutThread-4-for-ProvisionDevice(020232abc2931127)  [host]> /b/c/b/android_webview_arm64_aosp_perf_bisect/src/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 020232abc2931127 root
E   99.415s ProvisionDevice(020232abc2931127)  Failed to provision device 020232abc2931127. Adding to blacklist.

This is correctly blocked on 713883. I landed a fix for that this morning; we'll see how it fares.

No device status errors since https://codereview.chromium.org/2856253007 landed. There have been provision_devices failures, but in all of those cases, the build appears to have been killed. Marking as fixed; reopen on recurrence.