Sometimes a Chromium build will be serialized such that only a few
commands are running. This can be analyzed after the fact with
post_build_ninja_summary.py from depot_tools or with ninjatracing,
but it is also nice to be able to find out in the moment what commands
are running.
Running buildstate will find all running ninja.exe commands and will
print their child processes (direct children only). This was used to
find that this target:
gen/content/browser/devtools/devtools_resources_grit.d.stamp
takes almost a minute to build and can serialize the build.
Bug: 1162467
Change-Id: I3ac6406b1284dfa58ce243e7d8a89f79a0634af8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2645638
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#850909}