mollyim/webrtc
1
0
Fork 0
mirror of https://github.com/mollyim/webrtc.git synced 2025-05-19 08:37:54 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
webrtc/tools_webrtc/mb
History
Edward Lemur 2b67f5c65f MB: Add a way to run tests on swarming without using gtest-parallel. 
Adds a new test_type 'raw' to run tests on swarming without wrapping it
on gtest-parallel.

This will be used to run webrtc_perf_tests directly.

Bug: chromium:755660
Change-Id: I8558faadf242d1db1ad3e13083941886c92b1bd9
Reviewed-on: https://webrtc-review.googlesource.com/49360
Reviewed-by: Patrik Höglund <phoglund@webrtc.org>
Commit-Queue: Edward Lemur <ehmaldonado@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#21962}
2018-02-08 19:37:19 +00:00
..
docs Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
gn_isolate_map.pyl Reland "Make it possible to run video_quality_loopback_test in swarming." 2018-01-23 13:03:17 +00:00
mb Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.bat Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
mb.py MB: Add a way to run tests on swarming without using gtest-parallel. 2018-02-08 19:37:19 +00:00
mb_config.pyl Do not build h264 on Linux32 Debug bots. 2018-01-04 08:40:58 +00:00
mb_unittest.py MB: Add a way to run tests on swarming without using gtest-parallel. 2018-02-08 19:37:19 +00:00
OWNERS Add phoglund@ to various OWNERS and remove kjellander@ 2017-10-19 09:21:12 +00:00
PRESUBMIT.py Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00
README.md Rename tools-webrtc -> tools_webrtc 2017-05-09 06:30:13 +00:00

README.md

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:

  1. "gen" - the main gyp_chromium / gn gen invocation that generates the Ninja files needed for the build.

  2. "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: