commit 36439d67635a297ca0923b4b6aa8fa2703e7e314
author Patrik Höglund <phoglund@chromium.org> Mon Nov 14 13:15:36 2016 +0100
committer chrome-bot <chrome-bot@chromium.org> Mon Nov 14 16:42:25 2016 -0800
tree 11e0f4e8d4ee1c643aa8f7cf2af32bf4f29ffdf6
parent 6971b1811c477104bdcd440686757718893e341a

Correct WebRTC telemetry test name on the runner whitelist.

I don't know what this whitelist does, but it seems a likely
candidate for fixing our blocked telemetry uploads (?).

BUG=chromium:659562
TEST=can't test, config change

Change-Id: Id2a8a94bc491a2bc96dd3e76e9f88d4555cdc0d9
Reviewed-on: https://chromium-review.googlesource.com/411101
Commit-Ready: Rohit Makasana <rohitbm@chromium.org>
Tested-by: Rohit Makasana <rohitbm@chromium.org>
Reviewed-by: Rohit Makasana <rohitbm@chromium.org>

server/cros/telemetry_runner.py

diff --git a/server/cros/telemetry_runner.py b/server/cros/telemetry_runner.py
index 8bfbf7f..95ad5b5 100644
--- a/server/cros/telemetry_runner.py
+++ b/server/cros/telemetry_runner.py
@@ -60,7 +60,7 @@
                      'startup.cold.blank_page',
                      'sunspider',
                      'tab_switching.top_10',
-                     'webrtc.webrtc_cases']
+                     'webrtc.peerconnection']
 
 # BLACK LIST
 #  'session_restore.cold.typical_25', # profile generator not implemented on