[Ozone] Fix Vaapi unittest builds

[Ozone] Fix Vaapi unittest builds

BUG=none

Committed: https://crrev.com/638dcf8ea48510475248361caeca547c4541b950
Cr-Commit-Position: refs/heads/master@{#320758}

[dnicoara, 2015-03-16 17:37:20]

dnicoara@chromium.org changed reviewers:
+ spang@chromium.org

[spang, 2015-03-16 17:38:20]

lgtm

[dnicoara, 2015-03-16 18:22:43]

The CQ bit was checked by dnicoara@chromium.org

[commit-bot: I haz the power, 2015-03-16 18:23:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1014623003/1

[commit-bot: I haz the power, 2015-03-16 18:35:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-16 18:39:47]

Patchset 1 (id:??) landed as
https://crrev.com/638dcf8ea48510475248361caeca547c4541b950
Cr-Commit-Position: refs/heads/master@{#320758}

[spang, 2015-03-17 20:22:39]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1012213002/ by spang@chromium.org.

The reason for reverting is: Breaks CrOS !ozone build..

[Adrian Kuegel, 2015-03-18 08:57:41]

On 2015/03/17 20:22:39, spang wrote:
> A revert of this CL (patchset #1 id:1) has been created in
> https://codereview.chromium.org/1012213002/ by mailto:spang@chromium.org.
> 
> The reason for reverting is: Breaks CrOS !ozone build..

So what is the proper way to fix the broken ozone build? This is currently
affecting the Codesearch bots, because I enabled ozone there.

[dnicoara, 2015-03-18 12:33:29]

On 2015/03/18 08:57:41, Adrian Kuegel wrote:
> On 2015/03/17 20:22:39, spang wrote:
> > A revert of this CL (patchset #1 id:1) has been created in
> > https://codereview.chromium.org/1012213002/ by mailto:spang@chromium.org.
> > 
> > The reason for reverting is: Breaks CrOS !ozone build..
> 
> So what is the proper way to fix the broken ozone build? This is currently
> affecting the Codesearch bots, because I enabled ozone there.

Fix is at https://codereview.chromium.org/1017843002/