GitLab

The former way to enable kVaapiVp9Encoder in VEA unittest is wrong. It enables
kVaapiVp9Encoder in the begging of main() function in the test. Features are
overwritten later by base::TestSuite::Initialize(). Furthermore, it is too late
if the feature is enabled in each test case. base::TestSuite::Initialize()
queries the driver and the obtained capabilities will be used in the test case.
Hence, we have to enable kVaapiVp9Encoder between base::TestSuite::Initialize()
and media::VaapiWrapper::PreSandboxInitialization().

Bug: 811912, 930532
Test: VEA unittest with VP9 stream
Change-Id: Id1601d5ce985c189820f380df5c2e23ea265e17c
Reviewed-on: https://chromium-review.googlesource.com/c/1490987
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: Pawel Osciak <posciak@chromium.org>
Auto-Submit: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Pawel Osciak <posciak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#635945}