perezju, can you PTAL? This has flaked for 6 tryjobs today.

Detected 3 new flakes for test/step "telemetry.core.tracing_controller_unittest.TracingControllerTest.testFlushTracing". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyXAsSBUZsYWtlIlF0ZWxlbWV0cnkuY29yZS50cmFjaW5nX2NvbnRyb2xsZXJfdW5pdHRlc3QuVHJhY2luZ0NvbnRyb2xsZXJUZXN0LnRlc3RGbHVzaFRyYWNpbmcM. This message was posted automatically by the chromium-try-flakes app.

Detected 3 new flakes for test/step "telemetry.core.tracing_controller_unittest.TracingControllerTest.testFlushTracing". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyXAsSBUZsYWtlIlF0ZWxlbWV0cnkuY29yZS50cmFjaW5nX2NvbnRyb2xsZXJfdW5pdHRlc3QuVHJhY2luZ0NvbnRyb2xsZXJUZXN0LnRlc3RGbHVzaFRyYWNpbmcM. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Sheriff Bug Queue (unless already there).

+Ned FYI - haven't had time to look into this.

This test should be fixed ASAP or disabled. I don't know how to disable it, apart from removing it.

I will disable it for now

A failing log:
https://chromium-swarm.appspot.com/task?id=3cf4f51d2f17f810&refresh=10

 Trace config file string: {"trace_config": {"record_mode": "record-as-much-as-possible"}}
  Start Tracing Request: {'params': {'transferMode': 'ReturnAsStream', 'traceConfig': {'recordMode': 'recordAsMuchAsPossible'}}, 'method': 'Tracing.start'}
  Chrome version: 3401
  Trace config file string: {"trace_config": {"record_mode": "record-as-much-as-possible"}}
  Start Tracing Request: {'params': {'transferMode': 'ReturnAsStream', 'traceConfig': {'recordMode': 'recordAsMuchAsPossible'}}, 'method': 'Tracing.start'}
  Chrome version: 3401
  Trace config file string: {"trace_config": {"record_mode": "record-as-much-as-possible"}}
  Start Tracing Request: {'params': {'transferMode': 'ReturnAsStream', 'traceConfig': {'recordMode': 'recordAsMuchAsPossible'}}, 'method': 'Tracing.start'}
  Chrome version: 3401
  *************** BROWSER STANDARD OUTPUT ***************
  
  *********** END OF BROWSER STANDARD OUTPUT ************
  ********************* BROWSER LOG *********************
  No log file
  ***************** END OF BROWSER LOG ******************
  Closing browser (pid=4772) ...
  Did not find any windows owned by target process
  Browser is closed.
  Traceback (most recent call last):
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\testing\browser_test_case.py", line 39, in WrappedMethod
      method(self)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\decorators.py", line 208, in wrapper
      func(*args, **kwargs)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\core\tracing_controller_unittest.py", line 94, in testFlushTracing
      tracing_controller.FlushTracing()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\core\tracing_controller.py", line 62, in FlushTracing
      self._tracing_controller_backend.FlushTracing()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py", line 187, in FlushTracing
      '\n'.join(raised_exception_messages))
  TracingException: Exceptions raised when trying to flush tracing:
  Traceback (most recent call last):
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_controller_backend.py", line 179, in FlushTracing
      self._current_state.builder)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py", line 322, in FlushAgentTracing
      self.CollectAgentTraceData(trace_data_builder)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py", line 250, in CollectAgentTraceData
      '\n'.join(raised_exception_messages))
  ChromeTracingStoppedError: Exceptions raised when trying to collect Chrome devtool tracing:
  Error when collecting Chrome tracing on devtools at port 64008:
  Traceback (most recent call last):
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\platform\tracing_agent\chrome_tracing_agent.py", line 239, in CollectAgentTraceData
      client.CollectChromeTracingData(trace_data_builder)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\devtools_client_backend.py", line 462, in CollectChromeTracingData
      self._tracing_backend.CollectTraceData(trace_data_builder, timeout)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\tracing_backend.py", line 231, in CollectTraceData
      self._CollectTracingData(trace_data_builder, timeout)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\tracing_backend.py", line 259, in _CollectTracingData
      traceback.format_exc())
  TracingUnrecoverableException: Exception raised while collecting tracing data:
  Traceback (most recent call last):
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\tracing_backend.py", line 252, in _CollectTracingData
      self._inspector_websocket.DispatchNotifications(timeout)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_websocket.py", line 140, in DispatchNotifications
      self._Receive(timeout)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_websocket.py", line 155, in _Receive
      data = self._socket.recv()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_core.py", line 293, in recv
      opcode, data = self.recv_data()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_core.py", line 310, in recv_data
      opcode, frame = self.recv_data_frame(control_frame)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_core.py", line 323, in recv_data_frame
      frame = self.recv_frame()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_core.py", line 357, in recv_frame
      return self.frame_buffer.recv_frame()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_abnf.py", line 336, in recv_frame
      self.recv_header()
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_abnf.py", line 286, in recv_header
      header = self.recv_strict(2)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_abnf.py", line 371, in recv_strict
      bytes_ = self.recv(min(16384, shortage))
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_core.py", line 427, in _recv
      return recv(self.sock, bufsize)
    File "e:\b\s\w\ir\third_party\catapult\telemetry\third_party\websocket-client\websocket\_socket.py", line 80, in recv
      bytes_ = sock.recv(bufsize)
  error: [Errno 10054] An existing connection was forcibly closed by the remote host
  
  
  

Detected 5 new flakes for test/step "telemetry.core.tracing_controller_unittest.TracingControllerTest.testFlushTracing". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyXAsSBUZsYWtlIlF0ZWxlbWV0cnkuY29yZS50cmFjaW5nX2NvbnRyb2xsZXJfdW5pdHRlc3QuVHJhY2luZ0NvbnRyb2xsZXJUZXN0LnRlc3RGbHVzaFRyYWNpbmcM. This message was posted automatically by the chromium-try-flakes app.

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

commit 28f445af33ee82d2c4e68e6f5fc4dd3b1da36c86
Author: Nghia Nguyen <nednguyen@google.com>
Date: Thu Apr 19 19:49:10 2018

Disable TracingControllerTest.testFlushTracing on Win

Bug:chromium:829976
Change-Id: I09e1c3fcf40b7107aabf2c86e057a9392e513a77
TBR=perezju@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1020142
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>

[modify] https://crrev.com/28f445af33ee82d2c4e68e6f5fc4dd3b1da36c86/telemetry/telemetry/core/tracing_controller_unittest.py

So this is on Win? I'm not sure if I'm the right person to look at this (and currently swamped). Could we find another owner?

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

commit c145af9a6447af45691c1d8b3212979582dfa151
Author: catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Apr 19 21:58:12 2018

Roll src/third_party/catapult/ 4fe4dbb4d..28f445af3 (1 commit)

https://chromium.googlesource.com/catapult.git/+log/4fe4dbb4de4b..28f445af33ee

$ git log 4fe4dbb4d..28f445af3 --date=short --no-merges --format='%ad %ae %s'
2018-04-19 nednguyen Disable TracingControllerTest.testFlushTracing on Win

Created with:
  roll-dep src/third_party/catapult
BUG=chromium:829976


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.


TBR=sullivan@chromium.org

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