commit | 20c98232572eae6b81cf105ffa38352fe1fde962 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Tue Mar 29 15:00:52 2022 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 30 02:39:39 2022 +0000 |
tree | 51a4f32a3d7de3f5724b06ad09e120e458870b40 | |
parent | 0e13b6c8f2a253b1f037b8e232f8b2076bb8c5ec [diff] |
checkout: Always update initialized submodules Always update initialized submodules in the cache. We may not be including submodules in the current checkout, but they could be there from a past use of this cache, and could be out of date. Instead of deinitializing them, update them. Presumably they're not too far out of date, so this should be a pretty cheap operation. Bug: b/227379027 Change-Id: I49362dc26953cdbe6614a9284d6324e39edc7ecb Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/89340 Reviewed-by: Marc-Antoine Ruel <maruel@google.com> Reviewed-by: Ted Pudlik <tpudlik@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Rob Mohr <mohrr@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.