Findit identified the culprit r623581 as introducing flaky test(s)
summarized in https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Please revert the culprit or disable the test(s) asap. If you are the owner,
please fix!

If the culprit above is wrong, please file a bug using this link:
https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Analyzer%20-%20Wrong%20culprit%20r623581&comment=Link%20to%20Culprit%3A%20https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).

Findit identified the culprit r623581 as introducing flaky test(s)
summarized in https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Please revert the culprit or disable the test(s) asap. If you are the owner,
please fix!

If the culprit above is wrong, please file a bug using this link:
https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Analyzer%20-%20Wrong%20culprit%20r623581&comment=Link%20to%20Culprit%3A%20https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).

Assigned, marked as flake. Removing from sheriff queue.

ossu, can you take a look?

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

commit 2b8968669d64988de311baa42026fb5214ed38c1
Author: Ian Clelland <iclelland@chromium.org>
Date: Thu Jan 17 17:17:44 2019

Mark wpt/wrbtrc/RTCPeerConnection-track-stats as flaky

TBR: ossu@chromium.org
Bug: 922955
Change-Id: Ic0853722cdeb501e9d2479a7838ec10f1e46d63a
Reviewed-on: https://chromium-review.googlesource.com/c/1417359
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Auto-Submit: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#623731}
[modify] https://crrev.com/2b8968669d64988de311baa42026fb5214ed38c1/third_party/blink/web_tests/TestExpectations

Findit identified the culprit r623581 as introducing flaky test(s)
summarized in https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Please revert the culprit or disable the test(s) asap. If you are the owner,
please fix!

If the culprit above is wrong, please file a bug using this link:
https://bugs.chromium.org/p/chromium/issues/entry?status=Unconfirmed&labels=Pri-1,Test-Findit-Wrong&components=Tools%3ETest%3EFindit%3EFlakiness&summary=%5BFindit%5D%20Flake%20Analyzer%20-%20Wrong%20culprit%20r623581&comment=Link%20to%20Culprit%3A%20https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vYzI4MDI0ODc0OGNmZGFlMjI0MzAwZjRlZGYzOGUwOWIyZTQ1ZGIxYgw

Automatically posted by the findit-for-me app (https://goo.gl/Ot9f7N).

I'm guessing either [1] or [2] is the cause of the breakage. The logs just mention the failure is:

  01:50:16.810 3155 [20/20] external/wpt/webrtc/RTCPeerConnection-track-stats.https.html failed unexpectedly (text diff)

and those CL look like the only ones in the roll that affect stats. Since only one of the authors have a chromium account, I'll reassign to them for now, to take a look.

[1] https://webrtc-review.googlesource.com/c/src/+/117320
[2] https://webrtc-review.googlesource.com/c/src/+/117661

I expect the WebRTC changes just require the Chromium test to be updated, not that the CLs themselves are at fault.