Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of charliea@chromium.org

rendering.desktop/gmail in rendering.desktop failing on chromium.perf/Win 10 Perf

Builders failed on: 
- Win 10 Perf: 
  https://ci.chromium.org/buildbot/chromium.perf/Win%2010%20Perf

The failure looks like we're timing out at IsJavascriptExpressionTrue:

File "c:\b\s\w\ir\tools\perf\page_sets\top_25_smooth.py", line 44, in RunPageInteractions
    'window.__scrollableElementForTelemetry != null')
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\actions\action_runner.py", line 261, in WaitForJavaScriptCondition
    return self._tab.WaitForJavaScriptCondition(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\browser\web_contents.py", line 239, in WaitForJavaScriptCondition
    return self._inspector_backend.WaitForJavaScriptCondition(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\common\py_trace_event\py_trace_event\trace_event_impl\decorators.py", line 75, in traced_function
    return func(*args, **kwargs)
  File "c:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py", line 302, in WaitForJavaScriptCondition
    e.message + '\n' + debug_message)
TimeoutException: Timed out while waiting 60s for IsJavaScriptExpressionTrue.

Based on the flakiness dashboard, it looks like there's a bimodal distribution of how long this test takes to run, even when it passes: https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=rendering.desktop&builder=chromium.perf%3AWin%2010%20Perf

I suspect that, to fix the flakiness, either this bimodal distribution needs to be fixed or we need to extend that 60s timeout

This has been happening as far back as the flakiness dashboard seems to have history. I'm going to go ahead and disable the story and assign this bug to the benchmark owners.