Move `win-arm64-builder-perf` to 'chromium.perf' group.

Bug: 447622530
Change-Id: I0c4837c8c331632b4674200fb8bb2cf4f926301e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7000767
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Farid (Mojtaba) Faridzad <faridzad@google.com>
Cr-Commit-Position: refs/heads/main@{#1522954}
NOKEYCHECK=True
GitOrigin-RevId: e9c500c02570b67d6f67a4d8ce9a861507ab3931
3 files changed
tree: f878e4975d8da50c65ddc937c0ac615b92d2ad4e
  1. docs/
  2. lib/
  3. mb_config_expectations/
  4. __init__.py
  5. DIR_METADATA
  6. mb
  7. mb.bat
  8. mb.py
  9. mb_config.pyl
  10. mb_unittest.py
  11. mb_validation_unittest.py
  12. OWNERS
  13. PRESUBMIT.py
  14. README.md
  15. rts_banned_suites.json
README.md

MB - The Meta-Build wrapper

MB is a simple wrapper around the GN build tool.

It was originally written as part of the GYP->GN migration, in order to provide a uniform interface to either GYP or GN, such that users and bots can call one script and not need to worry about whether a given bot was meant to use GN or GYP.

It eventually grew additional functionality and is now still used even though everything is GN-only.

It supports two main functions:

  1. “gen” - the main gn gen invocation that generates the Ninja files needed for the build.

  2. “analyze” - the step that takes a list of modified files and a list of desired targets and reports which targets will need to be rebuilt.

We also use MB as a forcing function to collect all of the different build configurations that we actually support for Chromium builds into one place, in //tools/mb/mb_config.pyl.

For more information, see: