Do we normally run telemetry tests on the CQ? I thought we preferred browser tests for those?

Not media team but other teams have been running Telemetry tests on CQ.
1) chrome-benchmarking@ team run system health benchmarks on CQ for smoke testing.
2) GPu team use Telemetry to run WebGL correctness tests on CQ

It's nice to run Telemetry tests on the CQ so that the tests don't break as often. This will greatly reduce our workload as maintainers: we won't have to run bisect for benchmark failures and then go bug someone to fix something. Instead they will be notified before their CQ lands.

Also, since we already have to do the work to maintain these to make them work as performance tests, we may as well get the benefit of them running as functional tests as well to prevent bugs.

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

Has this been completed?  If not is it something we need/expect to do soon?
We need to take action or close as Won't Fix.