Example run: https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5X%20WebView%20Perf/builds/243 (search for "--device2")

My first thought is that the bot might just be down. However, this doesn't seem to be the case because several benchmarks are passing on the device (e.g. dramaeo.domcorequery, dromaeo.domcoretraverse, smoothness.simple_mobile_sites).

My second thought was that one particular benchmark might be taking a really long time to run, hogging all of the device's capacity and starving the other benchmarks of runtime. However, the benchmarks that succeeded aren't the first or the last ones to be scheduled. In addition, the sum of the duration of the benchmarks that didn't time out due to lack of capacity seems to be less than 20 minutes: far less than the 10 hour timeout.

Stephen, do you have any idea how to debug this? I'm very confused.