f00483206d
This reverts commit ec609b1cdd3ffd15c45445275899cf4010285399. Reason for revert: Investigate whether the correct builder is used for Pixel devices Original change's description: > Remove old Nexus perf bots > > Bug: b/236797526 > Change-Id: I3a3b88fb29ef8a8df074ead975c785a0bfbc84a7 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/287700 > Reviewed-by: Jeremy Leconte <jleconte@google.com> > Commit-Queue: Björn Terelius <terelius@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#38895} Bug: b/236797526 Change-Id: I3ca98ddc9a336fb91eec48d54a94ddff19038366 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/288240 Commit-Queue: Björn Terelius <terelius@webrtc.org> Auto-Submit: Björn Terelius <terelius@webrtc.org> Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#38898}
MB - The Meta-Build wrapper
MB is a simple wrapper intended 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 is meant to use GN or GYP.
It supports two main functions:
-
"gen" - the main
gyp_chromium/gn geninvocation that generates the Ninja files needed for the build. -
"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: