All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=861874

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=10436b62143e05474df5fecac4f81f87f3ca07ae205d45e0a2ec6ecdeea24b0e


Bot(s) for this bug's original alert(s):

mojo-linux-perf

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14df03eca40000

Commits range:
https://chromium.googlesource.com/chromium/src/+log/73fd6d6aecca2030d710ac12c3539099128a8a5a%5E..89f8047f0779227ae687109a7edceafca8d90f1e?pretty=fuller&n=1000

Seems to be caused by catapult autoroll (b5896b295b3238c960714f1aef991e022c0a45a0):
```
2018-07-07 nednguyen@google.com Set non blocking I/O read on ts_proxy subprocess stdout to make sure the timeout
```

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14df03eca40000

All of the runs failed. The most common error (7/20 runs) was:
AssertionError: loading.desktop.network_service requires --output-format=chartjson. Please contact owner to rewrite the benchmark if chartjTraceback (most recent call last):