[wptrunner] Create expectations for 'css/motion/'

This is part of a project [1] to run WPTs in Chromium with wptrunner,
the shared test harness, instead of 'run_web_tests.py'.

This change creates expectation data for WPTs in the ini-like format
wptrunner natively understands [2]. These expectations were created by
testing against content shell on Linux and gathering the results with a
rebaseline-like tool [3].

This change only affects experimental FYI builders, not CQ/sheriffed CI.
These files will not be upstreamed.

Analysis against ToT 'TestExpectations' and baselines:
  * 80 tests (2636 subtests) have exactly matching statuses.
  * 0 tests with flaky subtests were suppressed in
    'TestExpectations' because they could not be rebaselined. Now,
    suppressing flakes at the subtest level enables coverage for 0
    non-flaky subtests.
  * 0 tests have slightly different test-level statuses,
    probably due to flakiness or stale 'TestExpectations'.
  * 0 tests (0 subtests) have mismatched statuses.

[1]: https://docs.google.com/document/d/1VMt0CB8LO_oXHh7OIKsG-61j4nusxPnTuw1v6JqsixY/edit?usp=sharing&resourcekey=0-XbRB7-vjKAg5-s2hWhOPkA
[2]: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/testing/web_platform_tests_wptrunner.md#Expectations
[3]: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/tools/blinkpy/tool/commands/update_metadata.py

Bug: 1366074
Change-Id: I8e59b5e3f64c1b8f4ea4dcdbc5f29bbc739fe6f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3952956
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Commit-Queue: Jonathan Lee <jonathanjlee@google.com>
Auto-Submit: Jonathan Lee <jonathanjlee@google.com>
Cr-Commit-Position: refs/heads/main@{#1059329}
17 files changed
tree: 840343ff0b6104503f51e832417190b6e7101993
  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. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. DIR_METADATA
  68. ENG_REVIEW_OWNERS
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.

If you found a bug, please file it at https://crbug.com/new.