gclient runhooks seem to be working now. Let's wait to see the task finish.

It passes now. Probably it failed due to flakiness. Closing this one.

It just failed and closed the tree again.

https://logs.chromium.org/v/?s=chromium%2Fbb%2Fchromium.webkit%2FWebKit_Linux_Trusty_ASAN%2F12910%2F%2B%2Frecipes%2Fsteps%2Fgclient_runhooks%2F0%2Fstdout

The one that is currently building actually passes the gclient runhooks step: https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20ASAN/12911

OK. So the last build becomes green again. Let me try to figure out why gclient_runhooks is flaky.

And now it's 12 consecutive success.

@iannucci, are you familiar with this gclient runhooks flakiness due to "vpython src/third_party/catapult/telemetry/bin/fetch_telemetry_binary_dependencies"?

I think this failure is actually due to weirdness in the way the GCE python modules work and the way telemetry tries to download things; we were discussing this on go/cit-hangout yesterday.

nednguyen@, can you take a look and talk to hinoka@ and iannucci@ about this?

Removing from the sheriff and trooper queues in the meantime.

  File "/usr/lib/python2.7/dist-packages/google_compute_engine/boto/compute_auth.py", line 19, in <module>
    from google_compute_engine import logger
ImportError: No module named google_compute_engine

This is due to the script picking up the wrong GCE location. Note that this script is fetching data from cloud storage by executing https://cs.chromium.org/chromium/src/third_party/catapult/third_party/gsutil/gsutil?q=gsutil+f:catapult&dr=C&l=19 

Code: https://cs.chromium.org/chromium/src/third_party/catapult/common/py_utils/py_utils/cloud_storage.py?rcl=31767de5cf0a4baa96c28c90663276e165d86473&l=136

Robbie: should we update the args in the code above to use 'vpython' ...?

I think Ben's CL in https://chromium-review.googlesource.com/c/catapult/+/1110743 will fix this?