Invoke 'cros chrome-sdk' in gclient hooks via vpython3
This gets invoked outside of a cros chroot. And since it doesn't
specify which python to use today, it uses the system one. (ie: /usr/bin/python3)
It appears that recently the system python3 on some workstations
got upgraded. And the upgrade led to some mysterious errors in
simple chrome (see b/172226630#comment41 for details).
By invoking `cros chrome-sdk` via vpython, we use a version of python
that we more closely control, and so won't be affected by rollouts
we're not involved with. Additionally, using vpython's venv helps avoid
the original error that the rollout caused by using our own crcmod lib.
Bug: b/172226630
Change-Id: I0721843ab1294ad30750ae1122cb54b7a699a5d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4123032
Reviewed-by: Sven Zheng <[email protected]>
Commit-Queue: Ben Pastene <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1089345}
diff --git a/.vpython3 b/.vpython3
index 8872e87..76fc87e 100644
--- a/.vpython3
+++ b/.vpython3
@@ -260,6 +260,7 @@
# Used by:
# //third_party/blink/tools/wpt_upload.py
+# //third_party/chromite/bin/cros chrome-sdk
wheel: <
name: "infra/python/wheels/crcmod/${vpython_platform}"
version: "version:1.7.chromium.3"
