That's a gerrit feature request in that case. Isn't this easy to work around though? Just send the patch for review to yourself and that'll take it out of the WIP state?

Oh, by WIP CL I actually meant a CL that is not landed. So you cannot trigger tests on perf bots for a CL that is not merged into master AFAIK.

what I would like to be able to do is "git cl try -b <webrtc-perf-bot-name>".

Oh, right. The problem is that we don't have performance trybots. That's an interesting idea but I'm not sure how it would work.

I believe https://bugs.chromium.org/p/chromium/issues/detail?id=815076 will require implementing something that is, in practice, performance trybots.

I will leave this bug open for now, but I think we will more likely end up overhauling or deleting the tests you were having problems with.

I think that if the waterfall supports Swarming and LUCI, then it's possible to manually schedule what's normally a perf post-submit job, using `led`.

So I'd say this is blocked on LUCI migration.

I tried to make a "frankenstein monster" of a custom `led` run, but the first failure in the way is that the LUCI service account doesn't have access to bucket "chrome-webrtc-resources". It's not a big deal to fix, but it basically means starting work on LUCI migration.

I see, sure. My request is not time critical, it's just something I thought it would have been great to have when investigating those test failures. If it can be addressed as part of another planned task, even better.