Cannot test recipe changes on local machine due to missing logdog credentials |
|||
Issue descriptionIt seems that it is not possible to test recipes changes on local machine (running ./scripts/tools/run_recipe.py ...). When I try do do it I receive this error: slave.logdog_bootstrap.BootstrapError: Could not find service account credentials. Tried: /creds/service_accounts/service-account-luci-logdog-publisher.json There would probably be a way to skip logdog when running locally.
,
Feb 13 2017
Yes, here it is: > ./scripts/tools/run_recipe.py webrtc/ios_api_framework buildername="iOS API Framework Builder" mastername='client.webrtc' buildnumber=1
,
Feb 13 2017
I created this to solve the problem: https://chromium-review.googlesource.com/441988 However, the recommended way to try recipes is to use the "recipes.py run" command detailed in "setup_build"'s "run_recipe" step output.
,
Feb 14 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191 commit 4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191 Author: Dan Jacques <dnj@chromium.org> Date: Tue Feb 14 00:04:18 2017 Disable LogDog when using "run_recipe.py". LogDog bootstrapping shouldn't be used when running "annotated_run.py" via "run_recipe.py". BUG= chromium:691567 TEST=local - Ran it, works. Change-Id: I7c32990b41267734c2cf553cfd5ee8de0c4a4790 Reviewed-on: https://chromium-review.googlesource.com/441988 Commit-Queue: Daniel Jacques <dnj@chromium.org> Reviewed-by: Robbie Iannucci <iannucci@chromium.org> [modify] https://crrev.com/4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191/scripts/tools/run_recipe.py [modify] https://crrev.com/4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191/scripts/slave/logdog_bootstrap.py [modify] https://crrev.com/4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191/scripts/slave/unittests/annotated_run_test.py [modify] https://crrev.com/4b8c775fa5e79a1e066dcd5551f2f1bf79ad9191/scripts/slave/unittests/logdog_bootstrap_test.py
,
Feb 14 2017
This should be fixed now. However, still recommend running things the way I mentioned in #3.
,
Feb 14 2017
Thanks for the fix and for the advice. |
|||
►
Sign in to add a comment |
|||
Comment 1 by d...@chromium.org
, Feb 13 2017