Henrik: can you supply some nice filter so we don't have to run all of the tests?

We want to run external/wpt/webrtc/* and fast/peerconnection/* tests.

There are also other tests related to getUserMedia(), +guidou@ which ones do we want to run on webrtc.fyi?

What are the possibilities of having a webrtc CQ bot that runs only a few layout tests? Relatively often, probably once a week (I've got no numbers to back that up, could be wrong), someone makes a change in webrtc that breaks chromium, and more often than not that is a layout test.

It might be unorthodox to have bots of a different project run on the CQ or compiling might be slow (but not running if its filtered to just webrtc related tests) but it would be a great heads up and save people's time. If they accidentally break a test they have to learn about chromium anyway, so there's no point in delaying that.

Re #3: Technically it's no problem: we should be able to set that up similar to how I set up chromium compile-only bots. We have to watch what it does to cycle times though. Building chromium + running tests takes a lot longer than a WebRTC build+test cycle.

Artem, here is a pretty simple infra task for getting started with chrome infra work. Feel free to grab me when you have time and I'll explain how to do it.