commit | 88b6cbcc518f9260fbe61946a5d0be65fb333702 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Fri Dec 17 06:53:30 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 17 07:43:40 2021 +0000 |
tree | 861c127179b2b7c2a25e2262472fa30226cf0387 | |
parent | 630652cdae6d13cf40a29887099884997d081f06 [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia) into this repository. The build that created this CL was https://ci.chromium.org/b/8827618687643551793 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/6f1e73b239ba232d4a9351f56f53d6361dd89b94~..179288fb999a853cc4cf78ccbf3de2ee5be57707 6f1e73b (jessicacgu@google.com) [fxt] add guitar params in recipe e609e9f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 49bb8c2 (ihuh@google.com) [fuchsia_proto] Add use_ffx_experimental field. 214d281 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 179288f (jessicacgu@google.com) [fxt] Update recipes sdk to trigger Guitar project 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: I6306ee3bf22cdcf3753dc4eaaa6fd7ecb0e57368 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/75380 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.