The battery on 0a9f1772 is totally drained.  Currently charging back up and will re-attach when fully charged (tomorrow morning).   Will also be replacing the hub.

Just reattached 0a9f1772 and also replaced the hub. All devices are now getting ac charged.
Effective starting with https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%283%29/builds/883

Checking 09275b25...
  AC powered: true
  level: 100
Checking 0a9f1772...
  AC powered: true
  level: 100
Checking 09e28a6c...
  AC powered: true
  level: 100
Checking 0a38ca3e...
  AC powered: true
  level: 100
Checking 09e0cda5...
  AC powered: true
  level: 100
Checking 0a9f170a...
  AC powered: true
  level: 100
Checking 09e19f78...
  AC powered: true
  level: 100

Yay! The device is back up and running, but unfortunately another went down. I'll just add the info here rather than open a new issue.


Device 0 seems to be missing now, listed as "(error): missing" under device_status_check.

Provisioning is failing, followed by a number of failing tests:

media.mse_cases
media.mse_cases.reference
page_cycler.intl_es_fr_pt-br
page_cycler.intl_es_fr_pt-br.reference
speedometer
speedometer.reference

Logs show missing files as a common theme among these failures:

E    0.012s Main  File not found /b/build/slave/Android_Nexus7v2_Perf__3_/build/src/out/step_results/media.mse_cases

E    0.008s Main  File not found /b/build/slave/Android_Nexus7v2_Perf__3_/build/src/out/step_results/page_cycler.intl_es_fr_pt-BR

E    0.008s Main  File not found /b/build/slave/Android_Nexus7v2_Perf__3_/build/src/out/step_results/speedometer

Are these just test output files, implying that the tests have failed silently?

stip, can you answer the questions in #4?

I think those are all tests that run on device 0 which seems to be missing. Since they're not running, the persisted results wouldn't exist.

The bot has been green for two days now. Can we mark this as fixed?

2 days?   Amazing.

I say it's fixed (for now)