GitLab

Right now in FrameSequenceTracker::ReportMetrics, we compare the
throughput of the main thread vs the compositor thread, and report
the one with smaller throughput as the SlowerThread. There is an error
in the logic of determining which one is the slower thread. In
particular, currently we didn't consider the case where the compositor
and the main thread having the same throughput.

This CL fixes the error, and added a unit test.

Bug: None
Change-Id: Ib90b625665f508a8dab610a9ab07f90f6c4f1c58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838354
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703509}