commit | a4f20b9602b2ba91c007e32ae048088198f0e14b | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Fri Dec 10 06:52:14 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 10 07:37:52 2021 +0000 |
tree | fb548ae4caa9672f61878182712efea59b70c459 | |
parent | 79f0ab477ee90314f533bd3cbd4f6f5ca0353e34 [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/8828252867697640673 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/f6b7745d3a63d17c4250bbb84449efab84b08f89~..fafdd521de188dec037b171cf706e72eb396a720 f6b7745 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 7c92794 (olivernewman@google.com) [tricium_analyze] Update inclusive word replacements fafdd52 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/018cc81ee3693bbb39f23828e9419eba223d5829 018cc81 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from d62700d01d0c to e897e118887a 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 Bugdroid-Send-Email: False Change-Id: I3d6aa42f22ecef9553257398ca07d8be59def950 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/73460 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.