| commit | c5719eb114a7e5b3052f90d3a59e91c8ffc5cc0c | [log] [tgz] |
|---|---|---|
| author | Struan Shrimpton <sshrimp@google.com> | Wed Aug 06 22:59:14 2025 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 06 23:05:19 2025 |
| tree | 16ce3deebc59f78f1405415aad25e30e7f6e5e2e | |
| parent | 9edaf8da690d96866c1d96a357c868bd7c7b367e [diff] |
Readd blink_python_tests to rts_banned_suites This test looks like it was accidentally removed in https://crrev.com/c/6063046. Readd it. Bug: None Change-Id: Ia7dacf24c39eeadf4ec688e907f0ceaf0d8a4456 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6443165 Commit-Queue: Struan Shrimpton <sshrimp@google.com> Reviewed-by: Prakhar Asthana <pasthana@google.com> Cr-Commit-Position: refs/heads/main@{#1497905} NOKEYCHECK=True GitOrigin-RevId: 432bb055a23b4aaeec37fa8ada97c49639f116f5
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:
“gen” - the main gn gen invocation 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: