chromium/src
0
Fork 0
Code Activity

Remove mb.py try subcommand from docs

Browse Source 
The command was removed in https://crrev.com/c/4811739, and this removes
it from //tools/mb/docs/user_guide.md as well.

Bug: None
Change-Id: Id8b0fa77b71e8e4f3b05b387fa29131d0f87b682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6074689
Auto-Submit: Max Ihlenfeldt <max@igalia.com>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1392427}
This commit is contained in:
Max Ihlenfeldt
2024-12-05 19:01:57 +00:00
committed by Chromium LUCI CQ
parent efd05c63e5
commit d6204e9605
1 changed files with 0 additions and 20 deletions

20
tools/mb/docs/user_guide.md

@ -162,26 +162,6 @@ information on isolates and swarming.
In either case, any flags past `--` will be passed on to the command
to be run inside the isolate.
### mb try
Tries your change on the trybots. Right now this is essentially a fancy tryjob,
like one you could trigger via `git cl try` or via CQ dry runs. Basic usage is
`mb.py try -m tryserver.chromium.linux -b linux-rel base_unittests`
Your change must be uploaded to Gerrit. Local changes will not be uploaded for
you. It uses the gerrit CL associated with your given git branch.
You still have to specify the builder group(`--builder-group`) and buildername
(`-b`) arguments. See
[trybots.py](https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium_tests/trybots.py)
for a mapping of which bots are on which tryservers, and what those bots mirror.
Any trybot in `trybots.py` is supported; you can test your code on windows, for
example. The tryjob will compile and run your code on windows.
The target (`base_unittests`) in the example is a ninja build target. Most ninja
unittest targets can be put here which currently runs on the bots.
### mb validate
Does internal checking to make sure the config file is syntactically