Add whitelist preventing additions to legacy getStats() API.
Historically, new stats have bypassed stats OWNERs review and made it to Chrome stable. This will cause import breakages if stats are added to the legacy getStats() API in third_party/webrtc assuming: 1. They are present in a normal call setup, i.e. shows up in the scenario modelled by: WebRtcBrowserTest.RunsAudioVideoWebRTCCallInTwoTabsGetStatsCallback 2. The new stat does not recycle an already existing whitelisted name. // The run was green except for unrelated failures with // mac_chromium_rel_ng that have happened on multiple CLs NOTRY=True Bug: 822696 Change-Id: I2e6735ae6f1b987eb64865cb510eb65a6a1e4126 Reviewed-on: https://chromium-review.googlesource.com/1146726 Commit-Queue: Henrik Boström <hbos@chromium.org> Reviewed-by:Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/master@{#577178}
Showing
Please register or sign in to comment