17 MB must handle at least the `gen` and `analyze` steps on the bots, i.e.,
19 Ninja files, and the `analyze` step that takes a list of modified files
37 * `mb analyze -m tryserver.chromium.linux -b linux_rel /tmp/input.json /tmp/output.json`
60 ### Handling the analyze step
62 The interface to `mb analyze` is described in the
65 The way analyze works can be subtle and complicated (see below).
67 Since the interface basically mirrors the way the "analyze" step on the bots
75 ## Analyze  section in The MB (Meta-Build wrapper) design spec
77 The goal of the `analyze` step is to speed up the cycle time of the try servers
145 7. In some cases, we will not be able to correctly analyze the build graph to
199 * It normally doesn't make sense to call analyze at all if no files
211 * It doesn't make sense to call analyze if you don't want to compile
223 to analyze that we wanted to use no arguments instead of an empty
229 analyze code should also return an error code to the shell if appropriate
232 In the case where build files themselves are modified and analyze may
259 If a patch touches WebNode.cpp, then analyze gets as input: