Marking blocked bug to show impact. Trying to resolve the problem:
https://build.chromium.org/p/chromium.gpu/builders/Linux%20Release%20%28NVIDIA%29/builds/101529

Confused the build I'm interested in. But it doesn't matter, they all don't work:
https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.gpu%2FGPU_Linux_Builder%2F86226%2F%2B%2Frecipes%2Fsteps%2Fsetup_build%2F0%2Flogs%2Frun_recipe%2F0

I can't remember, what's our plan for making recipes work locally again?

Hm... I did this the other day and it was working... must have been a recent regression.

Yeah I just tried this locally and it works... something is going on. Can you provide any other details?

It looks like maybe your shell is expanding `-` to `/usr/local/google/home/machenbach/v8/infra/build/-` ?

Oh, derp... Just looked at the timestamps. I believe I already fixed this over the weekend.  Please re-open if this is still happening.

However, there are still a bunch of other problems with running the chromium recipes locally (see crbug.com/715350). They tend to make a lot of hard-coded assumptions about crap which don't apply to non-bots (stuff like https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/goma/api.py?q=goma/api.py+package:%5Echromium$&l=24).

Indeed now V8 recipes work again and Chromium gets an inch further, and then bails out with:
OSError: [Errno 13] Permission denied: '/b'

Is there another tracking bug for making the Chromium recipe work locally? If not, I reopen this one for that purpose.

It'd be sufficient for me to have a simple shell script that bootstraps a workstation to "look like a bot". Something like install-build-deps.sh for recipes.

I assume it's just a bit "new path here", "credential file there" kind of stuff...

Here the log of the current failure:
https://paste.googleplex.com/6433800930197504

Moving this one to client>chrome right now; the recipe engine itself does work with these suckers locally, but there are hard-coded assumptions in places in the modules that chrome uses that cause this to fail.

This may be fixed incidentally as we continue to push out luci lite and as  issue 649202  becomes resolved.

Closing this ticket should probably involve standing up an integration test on an unprovisioned bot (i.e. no special credentials) and verifying that this flow doesn't break. That, or we should be able to assert that the bot context === local developer context and so if it breaks for devs it breaks for bots (and vice versa).

Issue 648695 has been merged into this issue.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

With 'led' being really helpful, running locally isn't really required anymore in most cases in the future...

This isn't something we're realistically going to do any time soon.