We have an FYI simple chrome bot running telemetry_unittests along with some other unittests:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/chromeos-amd64-generic-rel-vm-tests?limit=200

Once we get this green, we should consider a standalone catapult trybot running just telemetry_unittests.

Ahh, was just about to file a bug for this; thanks for digging it up.

FTR, the tryserver is here:
https://build.chromium.org/p/tryserver.client.catapult/builders

It should really have a cros bot on there too, which I can get to. Only question is: would we want it running on VMs or real hardware? If hardware, it'd have to wait for bug 866062, which might be a while (~months).

They aren't doing actual measurements, so I think running in VMs is preferable.

Actually I lied. Most of the tryserver is here:
https://ci.chromium.org/p/catapult/builders/luci.catapult.try/Catapult%20Linux%20Tryserver
https://ci.chromium.org/p/catapult/builders/luci.catapult.try/Catapult%20Mac%20Tryserver
https://ci.chromium.org/p/catapult/builders/luci.catapult.try/Catapult%20Presubmit
https://ci.chromium.org/p/catapult/builders/luci.catapult.try/Catapult%20Windows%20Tryserver

Looks like it's been migrated to luci (except the android builder), so the new bot would go on there instead of the old buildbot instance.

We are actually thinking about moving telemetry from catapult to chromium/src/, so I would start this by adding telemetry_unittest on ChromeOS in Chromium waterfall instead

> so I would start this by adding telemetry_unittest on ChromeOS in Chromium waterfall instead

That would be  bug 836447 . But I'll leave this open until we come to a definite decision & plan wrt moving telemetry.

Ben, I'm having a hard time figuring out how long the telemetry_unittests and telemetry_perf_unittests stages take:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/chromeos-amd64-generic-rel/23163

Hopefully the times are within the bounds of the catapult CQ.

I think we're probably ready to have a chromeos catapult tryserver?

Ned: I haven't kept up to date on upcoming catapult plans, but the current setup (separate catapult branch + catapult roller into chromium third party) will be the setup going forward, is that right?

#8: achuith@, we actually consider moving Telemetry to chromium/src/ but it gonna be a while (issue 886939)

Thanks Ned - I thought I saw something along those lines. I suspect having a cros catapult tryserver in the interim is worthwhile then.