Ned, Ethan, can you please help find an owner for this?

Detected 5 new flakes for test/step "telemetry.web_perf.timeline_based_page_test_unittest.TimelineBasedPageTestTest.testTimelineBasedMeasurementGestureAdjustmentSmoke". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyjQELEgVGbGFrZSKBAXRlbGVtZXRyeS53ZWJfcGVyZi50aW1lbGluZV9iYXNlZF9wYWdlX3Rlc3RfdW5pdHRlc3QuVGltZWxpbmVCYXNlZFBhZ2VUZXN0VGVzdC50ZXN0VGltZWxpbmVCYXNlZE1lYXN1cmVtZW50R2VzdHVyZUFkanVzdG1lbnRTbW9rZQw. This message was posted automatically by the chromium-try-flakes app.

Sorry for the flake, disabling the test now

Failure log: 
  *************** BROWSER STANDARD OUTPUT ***************
  
  DevTools listening on ws://127.0.0.1:56118/devtools/browser/5635a5e1-c70f-47d1-8f4a-c487b9120b9c
  2018-06-06 22:47:26.020 Chromium[42555:2094883] *** Owner supplied to -[NSTrackingArea initWithRect:options:owner:userInfo:] referenced a deallocating object. Tracking area behavior is undefined. Break on NSTrackingAreaDeallocatingOwnerError to debug.
  [42560:775:0606/224726.071341:ERROR:vt_video_encode_accelerator_mac.cc(516)]  VTCompressionSessionCreate failed: -12908
  
  *********** END OF BROWSER STANDARD OUTPUT ************
  ********************* BROWSER LOG *********************
  No log file
  ***************** END OF BROWSER LOG ******************
  Taking screenshots upon failures disabled.
  Chrome version: 3453
  Failed to record clock sync marker with sync_id='4c62eb70-361b-41ef-a698-eabc8198c84d' via DevTools client <telemetry.internal.backends.chrome_inspector.devtools_client_backend.DevToolsClientBackend object at 0x11312d390>:
  Traceback (most recent call last):
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py", line 140, in _RecordClockSyncMarkerDevTools
      client.RecordChromeClockSyncMarker(sync_id)
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/devtools_client_backend.py", line 431, in RecordChromeClockSyncMarker
      assert self.is_tracing_running, 'Tracing must be running to clock sync.'
  AssertionError: Tracing must be running to clock sync.
  Try printing formatted exception: None None None
  
  Exception raised when cleaning story run: 
  
  Traceback (most recent call last):
    _RunStoryAndProcessErrorIfNeeded at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/story_runner.py:153
      test.DidRunStory(state.platform, results)
    DidRunStory at /b/s/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_measurement.py:289
      trace_result, _ = platform.tracing_controller.StopTracing()
    StopTracing at /b/s/w/ir/third_party/catapult/telemetry/telemetry/core/tracing_controller.py:53
      return self._tracing_controller_backend.StopTracing()
    StopTracing at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:130
      self._IssueClockSyncMarker()
    _IssueClockSyncMarker at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_controller_backend.py:234
      self._RecordIssuerClockSyncMarker)
    RecordClockSyncMarker at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:192
      devtools_clients)
    _RecordClockSyncMarkerDevTools at /b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/platform/tracing_agent/chrome_tracing_agent.py:149
      'Failed to issue clock sync to devtools client')
  ChromeClockSyncError: Failed to issue clock sync to devtools client
  
  Locals:
    client                                       : <telemetry.internal.backends.chrome_inspector.devtools_client_backend.DevToolsClientBackend object at 0x11312d390>
    devtools_clients                             : [<telemetry.internal.backends.chrome_inspector.devtools_client_backend.DevToolsClientBackend object at 0x11312d390>]
    has_clock_synced                             : False
    record_controller_clock_sync_marker_callback : <bound method TracingControllerBackend._RecordIssuerClockSyncMarker of <telemetry.internal.platform.tracing_controller_backend.TracingControllerBackend object at 0x110fff510>>
    sync_id                                      : '4c62eb70-361b-41ef-a698-eabc8198c84d'
    timestamp                                    : 32369536009.487
  
  Closing browser (pid=42555) ...
  Failed to gracefully shutdown.
  Proceed to kill the browser.
  Browser is closed.
  Traceback (most recent call last):
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/decorators.py", line 208, in wrapper
      func(*args, **kwargs)
    File "/b/s/w/ir/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_page_test_unittest.py", line 105, in testTimelineBasedMeasurementGestureAdjustmentSmoke
      self.assertFalse(results.had_failures)
  AssertionError: True is not false

Retrying failed tests (attempt #1 of 3)...

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

I don't see this test disabled on Mac, where all the current flakiness is.  Can you please disable it on Mac too?

code:
https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/web_perf/timeline_based_page_test_unittest.py?type=cs&q=TimelineBasedPageTestTest.testTimelineBasedMeasurementGestureAdjustmentSmoke&sq=package:chromium&g=0&l=92-95

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

commit 9150dda41f6b7c076f8ce3d9728d8e44b588fbe4
Author: Nghia Nguyen <nednguyen@google.com>
Date: Fri Jun 08 23:07:15 2018

Disable testTimelineBasedMeasurementGestureAdjustmentSmoke on Mac

Bug: chromium:850012
Change-Id: I1fd696166c8b02de271e7cce0e5edf7448efba14

TBR=charliea@chromium.org

Change-Id: I1fd696166c8b02de271e7cce0e5edf7448efba14
Reviewed-on: https://chromium-review.googlesource.com/1093874
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>

[modify] https://crrev.com/9150dda41f6b7c076f8ce3d9728d8e44b588fbe4/telemetry/telemetry/web_perf/timeline_based_page_test_unittest.py

Removing from sheriff queue

Detected 3 new flakes for test/step "telemetry.web_perf.timeline_based_page_test_unittest.TimelineBasedPageTestTest.testTimelineBasedMeasurementGestureAdjustmentSmoke". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyjQELEgVGbGFrZSKBAXRlbGVtZXRyeS53ZWJfcGVyZi50aW1lbGluZV9iYXNlZF9wYWdlX3Rlc3RfdW5pdHRlc3QuVGltZWxpbmVCYXNlZFBhZ2VUZXN0VGVzdC50ZXN0VGltZWxpbmVCYXNlZE1lYXN1cmVtZW50R2VzdHVyZUFkanVzdG1lbnRTbW9rZQw. 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).

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

commit b02d654c58f58c68d71e111c34ae5c2db15464e5
Author: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Sat Jun 09 04:20:02 2018

Roll src/third_party/catapult eca23c3..683dd05 (5 commits)

https://chromium.googlesource.com/catapult.git/+log/eca23c3..683dd05


git log eca23c3..683dd05 --date=short --no-merges --format='%ad %ae %s'
2018-06-09 dtu@chromium.org [pinpoint] Fix error in JobState.ScheduleWork().
2018-06-08 benjhayden@chromium.org Generalize the /api/alerts request handler.
2018-06-08 nednguyen@google.com Disable testTimelineBasedMeasurementGestureAdjustmentSmoke on Mac
2018-06-08 charliea@chromium.org Return 'improvement_direction' through the dashboard timeseries API
2018-06-08 benjhayden@chromium.org Fix a ZeroDivisionError in dashboard/alerts.py


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

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:850012
TBR=sullivan@chromium.org

Change-Id: I51a9a4738072e034e2839918e9fb28d83024fd55
Reviewed-on: https://chromium-review.googlesource.com/1094154
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@{#565847}
[modify] https://crrev.com/b02d654c58f58c68d71e111c34ae5c2db15464e5/DEPS