WebRTC: Update lkgr to new bots + cover chromium.webrtc.fyi

WebRTC: Update lkgr to new bots + cover chromium.webrtc.fyi

These updates will make it possible for WebRTC to setup auto-rolling
of WebRTC in Chromium's DEPS file.

BUG=433305
Committed: https://chromium.googlesource.com/infra/infra/+/9302eea8378f31c678fceedc3862ec040d6aa589

[kjellander_chromium, 2015-10-26 08:26:59]

kjellander@chromium.org changed reviewers:
+ machenbach@chromium.org

[kjellander_chromium, 2015-10-26 08:26:59]

Our LKGR is not used for anything else, but we should be able to use it for
auto-rolling WebRTC revision in Chromium DEPS.

Since both waterfalls are polling the same repo and the console views shows the
same revisions, this should work right?

The reason we want to know the status of the bots in chromium.webrtc.fyi before
rolling is that the bots in there have webcams and runs tests that doesn't run
in the regular Chromium CQ, and thus can detect errors that wouldn't otherwise
be caught pre-commit.

[Michael Achenbach, 2015-10-26 08:44:11]

lgtm - stamp

[Michael Achenbach, 2015-10-26 08:44:56]

> Since both waterfalls are polling the same repo and the console views shows
the
> same revisions, this should work right?

Guess it should. Chromium had always multiple waterfalls.

[kjellander_chromium, 2015-10-28 17:56:55]

The CQ bit was checked by kjellander@chromium.org

[commit-bot: I haz the power, 2015-10-28 17:57:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1416773007/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1416773007/1

[commit-bot: I haz the power, 2015-10-28 17:59:14]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-10-28 17:59:14]

Try jobs failed on following builders:
  Infra Presubmit on tryserver.infra (JOB_FAILED,
https://build.chromium.org/p/tryserver.infra/builders/Infra%20Presubmit/build...)

[kjellander_chromium, 2015-10-28 19:34:21]

kjellander@chromium.org changed reviewers:
+ estaab@chromium.org

[kjellander_chromium, 2015-10-28 19:34:22]

+estaab for OWNERS approval (apparently the OWNERS file in here was outdated as
well).

[estaab, 2015-10-28 19:45:02]

lgtm

[kjellander_chromium, 2015-10-28 19:46:11]

The CQ bit was checked by kjellander@chromium.org

[kjellander_chromium, 2015-10-28 19:46:11]

The patchset sent to the CQ was uploaded after l-g-t-m from
machenbach@chromium.org
Link to the patchset: https://codereview.chromium.org/1416773007/#ps20001
(title: "Update owners to cover .pyl files")

[commit-bot: I haz the power, 2015-10-28 19:46:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1416773007/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1416773007/20001

[commit-bot: I haz the power, 2015-10-28 19:48:07]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/infra/infra/+/9302eea8378f31c678fceedc3862e...

[kjellander_chromium, 2015-11-02 11:50:10]

A revert of this CL (patchset #2 id:20001) has been created in
https://codereview.chromium.org/1412133004/ by kjellander@chromium.org.

The reason for reverting is: This doesn't work as long as the got_revision
property for the builders in chromium.webrtc.fyi is a Chromium revision. 

Changing it to be the WebRTC revision is easy, but it will have the side-effect
of breaking the perf dashboard data reporting which is based on it. Since fixing
that problem is a larger problem, I'm reverting this for now.
.