0c15a09293
When we run webrtc_perf_tests with gtest-parallel, each test is run individually, and this results in the file with the perf results being overwritten each time. To avoid this, we won't use gtest-parallel when running webrtc_perf_tests, so we will simply run the binary directly. TBR=phoglund@chromium.org Bug: chromium:755660 Change-Id: I24db36e512fcf604a3de2adf4d0b4325b2c3d1ae Reviewed-on: https://webrtc-review.googlesource.com/49340 Reviewed-by: Edward Lemur <ehmaldonado@webrtc.org> Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org> Cr-Commit-Position: refs/heads/master@{#21982}
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: