We probably don't have too much control over these:
- nyan_big, nyan_kitty, nyan_blaze - close source userspace implementation from Nvidia,
- peach_pit, peach_pi, daisy_skate, daisy - old Exynos boards, without active support from Samsung anymore.

The above don't run ARC++, so our requirements for them should be much lower, I guess? Perhaps we could white list this test on them?

Bob is a member of the Gru (Rockchip RK3399) family, so we should be seeing the same problems with Kevin and Scarlet too. Is that not the case? For this one, the bitrate control is done by the libv4l plugin, so there is a chance we could fix it.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-kevin-private/+/d0bcd367b5cff3c01877df3b10520bc7f857169d

commit d0bcd367b5cff3c01877df3b10520bc7f857169d
Author: Chih-Yu Huang <akahuang@google.com>
Date: Wed Oct 03 03:02:57 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-bob-private/+/8a0cbdd04afdd34322ee1b7e796a78a100dc35c9

commit 8a0cbdd04afdd34322ee1b7e796a78a100dc35c9
Author: Chih-Yu Huang <akahuang@google.com>
Date: Wed Oct 03 03:02:58 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-scarlet-private/+/460d63bb0e8bc4b3723a55b18e8827fc96524d43

commit 460d63bb0e8bc4b3723a55b18e8827fc96524d43
Author: Chih-Yu Huang <akahuang@google.com>
Date: Wed Oct 03 06:39:05 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-kevin-private/+/24966610f81f15f6484840e20c687b9775a57e0f

commit 24966610f81f15f6484840e20c687b9775a57e0f
Author: Chih-Yu Huang <akahuang@google.com>
Date: Thu Oct 04 02:26:51 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-scarlet-private/+/808464118b14bdc64c6c8bf1f5774c6f86bfc669

commit 808464118b14bdc64c6c8bf1f5774c6f86bfc669
Author: Chih-Yu Huang <akahuang@google.com>
Date: Thu Oct 04 02:26:52 2018

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/overlay-bob-private/+/f633b12ff7d50d1567723ca09c1d78655e49287e

commit f633b12ff7d50d1567723ca09c1d78655e49287e
Author: Chih-Yu Huang <akahuang@google.com>
Date: Thu Oct 04 02:26:52 2018

Aka. Please whitelist the devices that we'll next fix in the autotest. The email alerts have lots of failures about this. They will hide the new regressions.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/c2aff028e627285d457c6a038737a082aa38f42d

commit c2aff028e627285d457c6a038737a082aa38f42d
Author: Chih-Yu Huang <akahuang@google.com>
Date: Wed Oct 10 12:19:40 2018

video_VideoEncodeAccelerator: whitelist the device for bitrate switch.

In video_VideoEncodeAccelerator, the bitrate switch test cases are
mainly for ARC++. However, some devices that do not run ARC++ failed
at those test cases. Moreover, we don't have much control over these
devices.

Therefore, we whitelist the boards that should pass the bitrate switch
test in this CL.

BUG= chromium:890125 
TEST=Pass video_VideoEncodeAccelerator autotest on scarlet

Change-Id: I397300586a1dd9e788de2401e4f2b936566f645f
Reviewed-on: https://chromium-review.googlesource.com/1270377
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Chih-Yu Huang <akahuang@chromium.org>
Reviewed-by: Chih-Yu Huang <akahuang@chromium.org>

[modify] https://crrev.com/c2aff028e627285d457c6a038737a082aa38f42d/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py

Turn out the Intel Rambi Bay Trial and Haswell also failed at this case. I will disable them as well

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/edda9fc4e08901b9418bbed4ba89a8f6a3db5cb1

commit edda9fc4e08901b9418bbed4ba89a8f6a3db5cb1
Author: Chih-Yu Huang <akahuang@google.com>
Date: Tue Oct 23 20:01:58 2018

video_VideoEncodeAccelerator: Change the whitelist for bitrate switch.

We didn't notice that Intel Baytrail and Haswell chipsets failed at
bitrate switch test case. We didn't enable ARC++ at them, so we
blacklist these devices.

Also, hana and elm are actually cannot pass the bitrate switch test.
(crbug/725087) We already filtered the test for them. Therefore we
remove hana and elm from the whitelist.

BUG= chromium:890125 
TEST=Pass video_VideoEncodeAccelerator autotest on scarlet

Change-Id: Iebc90fe04ea460a2548432de19f63680941498a6
Reviewed-on: https://chromium-review.googlesource.com/1288329
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Chih-Yu Huang <akahuang@chromium.org>
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>

[modify] https://crrev.com/edda9fc4e08901b9418bbed4ba89a8f6a3db5cb1/client/site_tests/video_VideoEncodeAccelerator/video_VideoEncodeAccelerator.py

All result went green from 11187.0.0.