Remove the 'gyp_config' concept from MB.
commitfae80e312dba6818315f4f8f0c3a1d85f6f4f9fb
authordpranke <dpranke@chromium.org>
Wed, 16 Sep 2015 00:16:19 +0000 (15 17:16 -0700)
committerCommit bot <commit-bot@chromium.org>
Wed, 16 Sep 2015 00:17:34 +0000 (16 00:17 +0000)
tree5eaf56f6b8cb0a8a6ac2e1b7bcec6d2400402ec1
parent4ce74f798e6e7c6fd944cf03aa0c6e69c427a736
Remove the 'gyp_config' concept from MB.

Previously MB would try to ensure that the build directory
passed to it matched the expected gyp configuration for the bot
(i.e. that we would not pass "//out/Debug" as a path for a
release bot).

Making this work correctly was awkward for the Win x64 bots
(which use Release_x64 instead of Release), and it's not clear
that this check would ever actually catch a real problem.

So, this patch deletes all of the 'gyp_config' logic instead
and simplifies things.

TBR=scottmg@chromium.org
BUG=481692

Review URL: https://codereview.chromium.org/1348463002

Cr-Commit-Position: refs/heads/master@{#349043}
tools/mb/docs/user_guide.md
tools/mb/mb.py
tools/mb/mb_config.pyl
tools/mb/mb_unittest.py