[Perf] Clean up config for linux-perf-calibration

The linux-perf-calibration builder has been deprecated for a while.

Bug: b:458164259
Change-Id: I901248db9cdf886cdb4729f0d1916b66ea33c072
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7125577
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1541016}
NOKEYCHECK=True
GitOrigin-RevId: 672ffb5ef082a9ede4158c38659ab15c7ec0e80c
2 files changed
tree: 05a7d995dc18ea86dccd39b8c2da306e2c721764
  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: