Issue 864295  has been merged into this issue.

nednguyen@: Could you take a look?

I'm also disabling the test on Windows: crrev.com/c/1139008

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/743af672d6a0543827834885cb0a8e8f4c988b8e

commit 743af672d6a0543827834885cb0a8e8f4c988b8e
Author: Xiaocheng Hu <xiaochengh@chromium.org>
Date: Tue Jul 17 01:09:38 2018

Disable WebPageReplayGoServerTest.testSmokeStartingWebPageReplayGoServer on Windows

Bug: chromium:864294
Change-Id: I3fe731b7ff27a9393d39dd9ab03de06e238d44e9
NoTry: True
Tbr: nednguyen@google.com
Reviewed-on: https://chromium-review.googlesource.com/1139008
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>

[modify] https://crrev.com/743af672d6a0543827834885cb0a8e8f4c988b8e/telemetry/telemetry/internal/util/webpagereplay_go_server_unittest.py

The auto-roll for Catapult is blocked now:
https://catapult-roll.skia.org/

Put Sheriff-Chromium label back before roll succeess

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

commit ee1d7d6a10afc8d71253cb849ed508f706cf92a9
Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Wed Jul 18 07:21:37 2018

Roll src/third_party/catapult f5342c4cf3d3..e8dc05ccba6b (9 commits)

https://chromium.googlesource.com/catapult.git/+log/f5342c4cf3d3..e8dc05ccba6b


git log f5342c4cf3d3..e8dc05ccba6b --date=short --no-merges --format='%ad %ae %s'
2018-07-18 nednguyen@google.com Revert "Handle stale directories when pushing files"
2018-07-18 nednguyen@google.com Implement screenshot capturing at system level on Linux
2018-07-17 dtu@chromium.org [pinpoint] Case-insensitive compare for Webview.
2018-07-17 simonhatch@chromium.org Dashboard - Whitelist documentation urls in /add_histograms
2018-07-17 cphlipot0@gmail.com [Systrace] Raise error when specified device is not found
2018-07-17 nednguyen@google.com Add test that verifies the way Telemetry generate skipped entries for filtered stories when benchmark is interrupted
2018-07-17 xiaochengh@chromium.org Disable WebPageReplayGoServerTest.testSmokeStartingWebPageReplayGoServer on Windows
2018-07-16 dtu@chromium.org [pinpoint] Update list of bots available in Pinpoint.
2018-07-16 bsheedy@chromium.org Handle stale directories when pushing files


Created with:
  gclient setdep -r src/third_party/catapult@e8dc05ccba6b

The AutoRoll server is located here: https://catapult-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG= chromium:862845 , chromium:862996 , chromium:863861 , chromium:860091 ,chromium:864294, chromium:863995 , chromium:862845 
TBR=sullivan@chromium.org

Change-Id: I5cab2a67db2dfee8c71f9ed7e445b82a9df41aec
Reviewed-on: https://chromium-review.googlesource.com/1141465
Reviewed-by: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#575965}
[modify] https://crrev.com/ee1d7d6a10afc8d71253cb849ed508f706cf92a9/DEPS

I'm not sure if it is related but since the test was fixed, the telemetry_unittests are timing out:
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29/1964

Telemetry unittest no longer fails in https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29/1965

It might be flaky. It timed out in 1964, 1963, 1962 and 1960. It passed in 1965 and 1961

It hasn't failed since 1965. Let's wait and see if it's fixed

Still timing out: 1968, 1969, 1973, 1975-1978, 1980, 1984, 1987 and 1988 all failed.