commit | 3926dff985b77eb81f42318b70a74fea3e2125fc | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu Apr 14 06:51:29 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 14 07:34:10 2022 +0000 |
tree | 7e4eadca908e162827a72a4028abee4132f1773c | |
parent | 2e87aa7fcae0048ea94c8f3354d59fa4c2c7b0c8 [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/8816928247178231617 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/a6eb94c12afd96af73f6e756d3dd119e7c3b6690~..d1039fe59d38f4fbf0957da061a71425eed3be99 a6eb94c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 82aa971 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest d1039fe (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/048f6f2fbb02fee8e69db6d41269c1f3b037403f 048f6f2 (chanli@chromium.org) [recipe-py] buildbucket: set `luci.buildbucket.parent_tracking`... More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: Ifad68e9689bf9babd773328e72b4768d49d726e5 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/91061 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.