commit | 57d037a6ecc416eb9edb2b7925a6f039f6577ca6 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Dec 07 18:48:33 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 07 19:28:08 2021 +0000 |
tree | d48db20e0d435d9f3fc273589c1040f178626030 | |
parent | 0db77f57c171c286c867e7cb393800551096383c [diff] |
Roll recipe dependencies (nontrivial). 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/8828479689564804593 Please review the expectation changes, and LGTM+CQ. fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/2c8bc3326fc972fc5a451a0f21fa744ba533a04b 2c8bc33 (mohrr@google.com) [git] Use --jobs with git submodule update More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com, tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ic4016e253d9686b8039e261a292f5c57d2ee80d5 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/72642 Reviewed-by: Rob Mohr <mohrr@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@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.