
Making video_capture_tests have the non_parallel_console_test_launcher type will pass --workers=1 to gtest-parallel, which ensures the tests execute sequentially. This is necessary now that we're accessing a real physical webcam, which is a system-wide resource that doesn't work well if several processes access it concurrently. Follow-ups: 1) get video_capture_test back up on Linux 2) drop sw webcams for Mac and Win 3) remove ensure_webcam_is_running.pu and surrounding machinery Bug: webrtc:9292 Change-Id: I5e3347ad234f6b942de736513075097d79c0fd36 Reviewed-on: https://webrtc-review.googlesource.com/94761 Reviewed-by: Oleh Prypin <oprypin@webrtc.org> Commit-Queue: Patrik Höglund <phoglund@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24325}
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 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: