Could this be related at all to the turning down of the s5s? They seem to be failing on the trigger step.

Interestingly the 5x perf bot is still getting triggered when the others are not.

We haven't turned down the S5s, yet. CLs are still in flight.

Looks like this started after the master restart at 11/16 18:38 PST
https://build.chromium.org/p/chromium.perf/json/clock?as_text=1

https://build.chromium.org/p/chromium.perf/builders/Android%20arm64%20Builder?numbuilds=200

Assigning this to benhenry@

https://chromium-review.googlesource.com/c/412079/ ?

Stephen, can you check if it's related to https://chromium-review.googlesource.com/c/412079/ ? 

 no scheduler: android_32 

Hey what about this https://chromium-review.googlesource.com/#/c/411338/

https://build.chromium.org/p/chromium.perf/builders/Android%20Builder/builds/122900 is before the breakage.

The N5X builder isn't triggered by the Android Builder bot anymore. So that's why it's still running.

https://build.chromium.org/p/chromium.perf/builders/Android%20Builder/builds/122914 is the first breakage (right after the purple for restarts).

These are back up.