Ping.

Yes, that's what the test should look like.

randy, I see an exception in the log that has to do with power monitoring:

Traceback (most recent call last):
  RunBenchmark at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\story_runner.py:366
    benchmark.ShouldTearDownStateAfterEachStorySetRun())
  Run at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\story_runner.py:244
    _RunStoryAndProcessErrorIfNeeded(story, results, state, test)
  _RunStoryAndProcessErrorIfNeeded at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\story_runner.py:89
    state.RunStory(results)
  traced_function at c:\b\s\w\irz8kl_a\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py:52
    return func(*args, **kwargs)
  RunStory at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\page\shared_page_state.py:301
    self._current_page, self._current_tab, results)
  traced_function at c:\b\s\w\irz8kl_a\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py:52
    return func(*args, **kwargs)
  ValidateAndMeasurePage at c:\b\s\w\irz8kl_a\tools\perf\measurements\webrtc.py:61
    self._power_metric.Stop(page, tab)
  Stop at c:\b\s\w\irz8kl_a\tools\perf\metrics\power.py:100
    self._StopInternal()
  _StopInternal at c:\b\s\w\irz8kl_a\tools\perf\metrics\power.py:52
    self._results = self._platform.StopMonitoringPower()
  StopMonitoringPower at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\core\platform.py:311
    ret_val = self._platform_backend.StopMonitoringPower()
  StopMonitoringPower at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\platform\win_platform_backend.py:365
    return self._power_monitor.StopMonitoringPower()
  StopMonitoringPower at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py:141
    power_statistics = super(MsrPowerMonitorWin, self).StopMonitoringPower()
  StopMonitoringPower at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py:51
    energy_consumption_j = self._PackageEnergyJoules() - self._start_energy_j
  _PackageEnergyJoules at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\platform\power_monitor\msr_power_monitor.py:73
    return (self._backend.ReadMsr(MSR_PKG_ENERGY_STATUS, 0, 32) *
  ReadMsr at c:\b\s\w\irz8kl_a\third_party\catapult\telemetry\telemetry\internal\platform\win_platform_backend.py:405
    response = sock.recv(8)
timeout: timed out



Could the bot be set up incorrectly?

Perfbot sheriff here: I'm disabling this test since there's been no action on the bug.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eaddab20f5caa0066c6ffa08113a59ee5f637e60

commit eaddab20f5caa0066c6ffa08113a59ee5f637e60
Author: sullivan <sullivan@chromium.org>
Date: Wed Apr 26 19:09:04 2017

Disabling failing webrtc.stress on Windows

BUG= 673581 

Review-Url: https://codereview.chromium.org/2844723002
Cr-Commit-Position: refs/heads/master@{#467404}

[modify] https://crrev.com/eaddab20f5caa0066c6ffa08113a59ee5f637e60/tools/perf/benchmarks/webrtc.py