commit | 5e9dc0c5c4cd1219a8bf345d5597d8d57a2c0201 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Mon Nov 28 23:29:56 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 28 23:29:56 2022 +0000 |
tree | d7ad698662b83460d4a0d5bf3b8c8b69b3b252af | |
parent | 8ac75c7fa1e093a4eb8c0348b524e422da186340 [diff] |
static_checks: Change how Readability works Readability is now enforced by Gerrit and not by recipes, so recipe code no longer fails if the Readability requirement isn't met. However, for CLs that make only trivial modifications to files covered by readability, recipes mark the CL as trivial, and Gerrit uses that to bypass the readability requirement. Bug: b/240290899 Change-Id: Icb16fe3456a3029f2281d39e87ae116f3533289d Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/121393 Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Ted Pudlik <tpudlik@google.com>
This repository contains recipes for Pigweed.
A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Pigweed and downstream projects using Pigweed in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Pigweed in your local environment.
See go/pigweed-recipe-docs for complete documentation and a guide for getting started with writing recipes.
The recommended way to get the source code is with git.
git clone https://pigweed.googlesource.com/infra/recipes
In most cases you will need a Chromium depot_tools checkout in your PATH
as well.
git clone https://chromium.googlesource.com/chromium/tools/depot_tools ~/depot_tools echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc
./presubmit.sh
runs three different sets of tests:
./recipes.py test train
)./black --diff --check .
).recipe_deps/fuchsia/scripts/cleanup_deps.py --check
)The formatting check will tell you what‘s wrong but not fix it. For that you need to run ./black .
. Similarly, the dependencies check will tell you what’s wrong but you'll need to edit the files to fix issues.
If not using ./presubmit.sh
you'll need to run ./scripts/ensure_black.sh
before ./black
is present.