tree 67886d96bb6a86fa2d899f498160eecd7214fe34
parent 29fd84afc090cd82e34cfea38d6b15d0ebc4bdf7
author Mohsen Izadi <mohsen@chromium.org> 1653495400 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1653495400 +0000

Reland: Report total event latency metrics to UI compositor

Whenever a presented frame in the browser compositor has associated
events, total latency for those events are reported back to UI
compositor. The UI compositor can decided if/how to report those
metrics.

This was originally landed as r1002811, but got reverted due to making a
bunch of interactive UI tests flaky. The reason for the flake was a
DCHECK that expected the presentation timestamp be strictly greater than
the event timestamp. However, it is conceivable that, at least in tests,
the two timestamps are equal. So, this reland changes the DCHECK to
expect the presentation timestamp is greater than or equal to the event
timestamp.

Bug: 1278417,1325180
Change-Id: I8e5719b5d6d81f7d3d15294a85016ade2b21ce26
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3650854
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Commit-Queue: Mohsen Izadi <mohsen@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1007406}