Google Git
Sign in
chromium / chromium / src / a5852f31d10e9953427969577cf147f04bfade6b
commita5852f31d10e9953427969577cf147f04bfade6b[log] [tgz]
authorMiguel Casas <mcasas@chromium.org>Tue May 25 20:03:42 2021
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue May 25 20:03:42 2021
treec27e503392be1267b6263854776151d6f5028fbd
parent0fdaf5cc5f44d9d5e628d5a4bb681e5ac87f20b9 [diff]
RELAND:media/gpu/vaapi: add Vaapi Vpp unittest

crrev/c/2890850 landed a new Vpp unittest but it failed on two backends,
namely i965 and AMD. This CL relands the CL leaving those two backends
as TO-DOs.

New changes in http://crrev.com/c/2917556/1..2

Test: vaapi_unittest --gtest_filter=*VaapiVppTest*  on reks (fails).

---- original CL description ------------------------------------------

This CL adds a VaapiVppTest with a single parameterized test case
to verify that the Video Processing Pipeline (Vpp) can be called
to convert (scale in this case) formats that claim to support.

Bug: b:187852384
Test: vaapi_unittest --gtest_filter=*VaapiVppTest*  on volteer

Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2890850
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#883539}
Change-Id: I42e4d0a1ddcb52d32849bc60ba83caf83238a791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2917556
Auto-Submit: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#886433}
1 file changed
tree: c27e503392be1267b6263854776151d6f5028fbd
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.