It came back on the next build so it may be a flake?  Will monitor the next few builds.

https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/4339

This bot is still failing. It is red about 10% of the time and purple the other 90% of the time.

It appears to be failing on different tests every time.

The bot is failing, yes.  But it is failing random tests on random devices.  For example, let's look at https://uberchromegw.corp.google.com/i/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/4664 

The only device which ran all it's test successfully was 0accf87325995bd0 (Device affinity 4).

Looking at other builds some devices go missing and then come back on the next build.  So there is some general flakiness.   What stabilized things with Android Nexus5 Perf (1) was switching out the host so that only usb3 was in the chain.

I'll do the same here.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome-golo/chrome-golo.git/+/721afe9627ac7a178ed12260d5f29c67d10dddc3

commit 721afe9627ac7a178ed12260d5f29c67d10dddc3
Author: Peter Schmidt <pschmidt@google.com>
Date: Thu Dec 22 19:14:44 2016

It's all usb3 all the way.  Starting with https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/4670 

Let's see if things settle down.

Ugh, now all the devices are being blacklisted due to authorization issues.

Fixing that.

Circling back on this.   All devices have been consistently online now but device affinity 3 (0acca27c25995770) seems to be failing various tests consistently.

I'm going to swap this N5 out.

Device replaced effective with https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%282%29/builds/4734

Looking back it's now 0d88d39743e4b8df that is listed as missing.  This was fixed earlier today in https://gutsv3.corp.google.com/#ticket/24765207

Waiting for a couple of more builds to see if things have settled down.

Devices appear to be stable now.