I suspect that this is the recording of the page having some problem (can be checked by looking at the devtool log & look at the network tab). 

The best here is probably just re-record the page.

We are still seeing failures on google stories on the Win7x64 and Win7 bots.
https://build.chromium.org/p/chromium.perf/builders/Win%207%20Perf
https://build.chromium.org/p/chromium.perf/builders/Win%207%20x64%20Perf

All the failures appear to be because they fail to log into google:
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_7-2017-11-15_01-07-5738627.png
https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/profiler-file-id_9-2017-11-15_01-07-5424152.png


This has been failing as far back as history goes on the two bots at this point.

Did anyone re-record the pages after Neds comments? Since these have been failing so long, with no comments on this bug; does anyone even care about these tests? If not, should we remove them? Upping priority a little. These have been failing for far too long.

Bot health sheriff: benchmark test breakages in general should be assigned to owner.

Victor: can you triage fixing these cases or removing them?

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

commit b45d15ba8b6fa1e66d1aa24b636b44792a804e61
Author: Charlie Andrews <charliea@chromium.org>
Date: Wed Nov 15 22:11:36 2017

Disable failing smoothness.top_25_smooth stories

TBR=rnephew@chromium.org, vmiura@chromium.org

Bug:  762165 , 736099
Change-Id: I8c0cfb765015a3efdc26ae4a548dd5164b4d483f
Reviewed-on: https://chromium-review.googlesource.com/769431
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Reviewed-by: rnephew <rnephew@chromium.org>
Cr-Commit-Position: refs/heads/master@{#516851}
[modify] https://crrev.com/b45d15ba8b6fa1e66d1aa24b636b44792a804e61/tools/perf/benchmarks/smoothness.py