commit | 2f104ddb60b8a7e51735d99a50a0be6868433ef3 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Dec 07 07:00:18 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 07 07:42:09 2021 +0000 |
tree | 36d27790b34dc4b1b067b6b4e0e811eb7d6b2239 | |
parent | 386949350a9893873c105e051e6a384f2a064f8b [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia, recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8828524655445984481 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/94d6dcd48fd9b4629bca498b3c76947292cba939 94d6dcd (atyfto@google.com) [fuchsia/build] Add ability to enforce size creep review recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/202ad55fc6b29aef8da502f55050afe8e2b12dc9~..841e0e7d3e74fcde212886e3465773d75dec9d2f 202ad55 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 6578c26ab505 to f58188e7754b 841e0e7 (tikuta@chromium.org) cas: update client revision More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I85a20b96e3e2c345bc89c9edd1efd965583eee35 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/72620 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.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.