| commit | 3af85bfe6e63b69e49efa221279eb52a1b575f37 | [log] [tgz] |
|---|---|---|
| author | Garrett Beaty <gbeaty@chromium.org> | Wed Aug 12 17:17:37 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 12 17:17:37 2020 |
| tree | 30ac65d61fedc5a3ad6ae86afcb46e1f0a9678d3 | |
| parent | 7afe2ac1235f041e623861b156e9014125952bcf [diff] |
Update the build example to refer to a fake file. The example recipe unnecessarily refers to an actual file but the recipe could never actually be executed because it's passing invalid flags in one of the calls. The presence of an actual script creates unexpected results when looking for usages of the actual script. Change-Id: Ica9d66fcc8197956725982aed5ad50a747b0f3ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2350501 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org>
If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*), please take a look at the README for more information pertaining to recipes.
The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores, with the exception of the special functions RunSteps and RunTests in recipes. Use yapf (git cl format) to autoformat new code.