It seems that the estimated_input_latency metric is causing regular failures on load:media:youtube on Mac Pro 10.11 Perf.

Here are some instances of this happening:

https://chromium-swarm.appspot.com/task?id=3ad56510f3aca410&refresh=10&show_raw=1

https://chromium-swarm.appspot.com/task?id=3ad56510f3aca410&refresh=10&show_raw=1

https://chromium-swarm.appspot.com/task?id=3ad31e928b5cd210&refresh=10&show_raw=1

The call stack generated is:

Traceback (most recent call last):
  File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/value/failure.py", line 41, in _GetExcInfoFromMessage
    raise Exception(message)
Exception: Error: The sliding window must fit in the specified time range
    at Object.maxExpectedQueueingTimeInSlidingWindow (/tracing/extras/chrome/estimated_input_latency.html:308:13)
    at addExpectedQueueingTimeMetric_ (/tracing/metrics/system_health/expected_queueing_time_metric.html:139:23)
    at new expectedQueueingTimeMetric (/tracing/metrics/system_health/expected_queueing_time_metric.html:85:5)
    at runMetrics (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:47:16)
    at metricMapFunction (/b/s/w/ir/third_party/catapult/tracing/tracing/metrics/metric_map_function.html:149:24)
    at Object.mapSingleTrace (/tracing/mre/map_single_trace.html:39:7)
    at eval (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:61:18)
    at Object.runAndConvertErrorsToFailures (/tracing/mre/map_single_trace.html:24:10)
    at mapSingleTraceWithResult (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:52:12)
    at Object.mapSingleTraceMain (/b/s/w/ir/third_party/catapult/tracing/tracing/mre/map_single_trace_cmdline.html:77:20)

dproy@, could you investigate this? In the meanwhile, I'm going to go ahead and disable the story in the meanwhile, and (for some reason) it doesn't seem to be happening elsewhere.