Chameleon | Cap at max frame count.

We use polling to stop capturing when the # of frames captured
has exceeded a specified maximum. Sometimes we still end up with
more frames than expected.

This causes unexpected/non-legit failures.

Solution:
Cap the total number of frames captured at the max specified.
If the polling stops when we have too many frames they will chopped.
If too little frames, then the lcs comparison will complain if the
frames were too few.

BUG=None.
TEST=Tested on falco, link.

Change-Id: I5c9f9c537fb7a6ad64b7e3013ea6703ee85e0c21
Previous-Reviewed-on: https://chromium-review.googlesource.com/312762
(cherry picked from commit 2d5e4a9ff84695be4bee073e743c5aa973d52927)
Reviewed-on: https://chromium-review.googlesource.com/312864
Reviewed-by: Mussa Kiroga <mussa@chromium.org>
Commit-Queue: Mussa Kiroga <mussa@chromium.org>
Tested-by: Mussa Kiroga <mussa@chromium.org>
1 file changed