GitLab

The previous change 973509d4, which
added querying of stream latency, incorrectly uses the device id
for querying the stream latency.

We must instead, first query the list of stream ids and query the
latency of a given stream. While there may be multiple streams,
we can't do anything with that information; e.g., to handle that
case we would need to attempt to synchronize all streams to the
highest latency. Apple instead recommends just taking the latency
of the first stream since that will cover the majority of cases.

BUG=783282
TEST=none

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I98b65b1fa7030f63abbb6d96c7540352d1bb896b
Reviewed-on: https://chromium-review.googlesource.com/802194Reviewed-by: Olga Sharonova <olka@chromium.org>
Commit-Queue: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#520988}