Start running chrome_ai_wpt_tests on Mac bots

This CL introduce a new testing step named "chrome_ai_wpt_tests" in the
optimization guide Mac bots (arm64, x64). We runs the test only on Mac
bots due to the very limited capacity for some of the linux/windows
machines.

To run only on Mac, this cl does followings:

1. In infra/config/targets/basic_suites.star:
  - Add a new generated_script `chrome_ai_wpt_tests`.
2. In infra/config/targets/tests.star:
  - Add a new isolated_script_test `chrome_ai_wpt_tests`.
3. In infra/config/targets/matrix_compound_suites.star:
  - Splits `optimization_guide_desktop_script_tests` which is shared
    with Mac bots (mac-arm64, mac-x64) and win-arm64 bots to
    `optimization_guide_mac_script_tests` and
    `optimization_guide_win_arm64_script_tests`.
  - Add `chrome_ai_wpt_tests_suite` in
    `optimization_guide_mac_script_tests`.
4. In testing/buildbot/waterfalls.pyl:
  - Use `optimization_guide_mac_script_tests` for Mac bots (mac-arm64,
    mac-x64).
  - Use `optimization_guide_win_arm64_script_tests` for win-arm64 bots.

Bug: 361192155
Change-Id: Ib66052d23c8f0ef6e3b227056909e9c66167e655
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5824117
Reviewed-by: Marco Georgaklis <mgeorgaklis@google.com>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1349675}
8 files changed
tree: 3b8f5ac4a8a3868f620338b8327fc7f2c216dbf1
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitallowed
  56. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. CPPLINT.cfg
  70. CRYPTO_OWNERS
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. 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.