commit | 22b95532ee2945672a71183bcf98b1af929d2b85 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Thu Jan 06 07:14:28 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 06 18:16:19 2022 +0000 |
tree | 32426a9925f308013725d9c803986c92d453c38c | |
parent | e1d553cb9f13d5158db06392049c9bc43aef10e8 [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/8825806749528736817 Please review the expectation changes, and LGTM+CQ. fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/4c8dd8e2fb88824e4f87e61d9c1bef47245eb12a 4c8dd8e (olivernewman@google.com) [git] Make get_changed_files return empty list if no files are... 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: I2db62c6f744387fe69dd04fe1a1a0ec5629ff793 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/77040 Reviewed-by: Rob Mohr <mohrr@google.com> Commit-Queue: Rob Mohr <mohrr@google.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.