I'm pretty sure it's because of remote_run. I didn't check yet, but I think the recipe uses direct paths to depot_tools. Instead, it should be using the path recipe module and use the explicitly exported paths from there. I don't remember the details at the moment, but can dig out if needed.
The code is making the assumption that you're in a tools/build checkout on a buildbot host, which is no longer true. This needs to be fixed.
Where does this code call gsutil?
Also, is this bot important? If so, it should be moved off of chromium.fyi.
Dug into this a bit. It's calling slave_utils.GSCopyFile, which can't find depot tools. I'm not sure what the best solution to this is....
cc-ing andybons@
The bot is important to V8 - it's staging a feature that we plan to launch soon. If there were a waterfall chromium.staging, I'd move it there. Otherwise, we could move it to the webkit waterfall as well if there's no problem with that. But it shouldn't be a tree closer.
Thanks, Stephen!
So this is now not a trooper issue, but before I remove it from the queue - who should own the long term fix? Could that person take the bug please?
Thanks!
I switched this back to "remote_run" after a change that I think will fix this specific problem. I'll be monitoring the FYI waterfall and will change this back if there is an observed problem.
Comment 1 by machenb...@chromium.org
, Nov 7 2016