Prune VirtualEnv's python from environment before running ninja_wrapper.

This should fix a problem where build targets are running with a default
vpython and missing modules available in the "parent" vpython
environment. See similar fix for gn.py in https://crrev.com/c/1120817.

BUG=982874
R=​iannucci@google.com, tikuta@google.com

Change-Id: I01929e1c4808b3ae43d1969d57ae15451ef68821
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1703299
Auto-Submit: Michael Moss <mmoss@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
(cherry picked from commit 8b52fef72fc4b24b8da2edc4014b5d1499a36667)
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/1703653
Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Michael Moss <mmoss@chromium.org>
1 file changed
tree: 4c16b8e662d1429b36ff2daaccaa7da2bde8e6a1
  1. infra/
  2. masters/
  3. scripts/
  4. site_config/
  5. slave/
  6. tests/
  7. third_party/
  8. .gitattributes
  9. .gitignore
  10. .vpython
  11. codereview.settings
  12. DEPS
  13. environment.cfg.py
  14. LICENSE
  15. OWNERS
  16. PRESUBMIT.py
  17. README.md
  18. WATCHLISTS
README.md

build

Hi build contributor! If you do any change in scripts/master/ or touching any master's html/ directories, you must restart master.chromium.fyi first and ensure that it still works before restarting other masters.

Recipes

If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.