commit | b71f6ed4ac3726e6c462610204c36552af2adade | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu Jun 09 00:02:14 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 09 00:36:48 2022 +0000 |
tree | 80a596d06c8c9130c9ac1bbc5f1385fd681dbc19 | |
parent | b82474dea5ffe9be376621838030d832f0bee004 [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/8811880562415183809 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/575367a64d5e73183cba58a0557b8a572350b3dc~..8db1471e050a42dd844c11558d3893a49e2d4870 575367a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest c786c97 (olivernewman@google.com) [auto_roller] Delete Options shim 8db1471 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/51b3aed56d1ba5b0e8ac65f94c20b15513a5f87c 51b3aed (jkusuma@google.com) Update go.chromium.org/luci protos related to resultdb. More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I4ee13fae126f65ae6aa5baba70ba3611df3303c8 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/97531 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.