commit | 124093e3bfecd564e3c7e0a1026f996749ba4029 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu May 19 02:30:18 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 19 03:05:08 2022 +0000 |
tree | a5a993b8494afbdd3c4df2f4bd91c218417684ae | |
parent | 1b25b93f5116b7177a0453154445ee2a17fb5f6e [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/8813773782193233601 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/a20f7782a66a6bd44213064556a596c7ec413128~..e28479ed2d0784b5160181c9fce973dd82deb9ad a20f778 (atyfto@google.com) [cipd_roller] Add prototype CIPD ensure file roller e28479e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/e3cd9ebd631fa88e0d6ecb9920ba0b6ed42a1325 e3cd9eb (kuanhuang@chromium.org) Add recipes API swarming.show_request(name, task) -> TaskRequest 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 Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I771e99b74ae470f8e7c0fa511876c8471e31d6ea Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/95260 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.