Relevant link to failing step: https://logs.chromium.org/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_One_Perf%2F1694%2F%2B%2Frecipes%2Fsteps%2Fdummy_benchmark.stable_benchmark_1.reference_Dashboard_Upload%2F0%2Fstdout

Relevant excerpt from logs:

Error: No perf dashboard JSON was produced.
!@@@STEP_FAILURE@@@
step returned non-zero exit code: 1

This is happening on the latest run on Nexus5 Perf (https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5%20Perf/1941) and Android One perf (https://ci.chromium.org/buildbot/chromium.perf/Android%20One%20Perf/1694), and I expect it will happen again on this run of Nexus 5X Perf (https://ci.chromium.org/buildbot/chromium.perf/Android%20Nexus5X%20Perf/1960).

Emily, do you know of anything on the OBBS side that may be causing this? Based on the failure log, this looks to be a problem with us producing the data rather than the dashboard consuming it.

Yes, this is a known issue,  crbug.com/859073 

There are two issues going on here.  The reference build is failing but we don't report red on that.  It is producing invalid perf results so the dashboard is rejecting it.  We shouldn't turn red on reference dashboard upload failures.

We don't investigate reference build failures. but we should fix the problem with dashboard uploads showing red.  This will be fixed in OBBS and android should be on OBBS in the next week or so.

The NextAction date has arrived: 2018-07-03