GitLab

Originally, we set a timeout for flush that starts at calling
VEA::Flush() and ends at flush callback is called. However, we don't
know how many pending frames in VEA when we call VEA::Flush(). The
delay may vary a lot due to the number of pending frames.

This CL changed to set timeout of each BitstreamBufferReady() call. We
could verify the time usage of each encoded bitstream buffer, and the
time period between the last bitstream buffer is returned and the
flush callback is called. It makes the unittest more robust.

BUG=chromium:979497
TEST=run video.EncodeAccelH2642160PI420 on celes

Change-Id: Ie52c9378397598aba5855d75553f7aef269bb4ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720122
Commit-Queue: Chih-Yu Huang <akahuang@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#688468}