awdf@ pointed out that some tests succeed even though they have the BattOr error (e.g. https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/43064). Therefore, maybe the BattOr isn't what is causing the telemetry_perf_unittests to fail.

Still, would it be possible to change how the error is displayed to avoid confusion?

Re-assigning to charliea@ who know about BattOr.

This doesn't seem to be still happening, or at least it's not still causing things to fail, so I'm clearing the Sheriff-Chromium label.

Un-CCing alexandermont@, as he's not on the team anymore.

rnephew@, any idea what might be happening here? Is this just an error that shows up in the log when we run a test that has optional battor tracing (e.g. system_health.common_mobile) without a battor attached?

The NextAction date has arrived: 2017-06-08

This is telemetry looking for a battor where one is not intended to exist.

Assigning this to rnephew@, who knows the most about this chunk of code.

Going to postpone this a week because I just assigned Randy about three bugs this morning and don't see any sense in completely swaming him with work.

The NextAction date has arrived: 2017-07-03

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot