| commit | 7fd1312321d6e9917fd82b86835d3776448afef5 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Sat May 28 04:00:16 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat May 28 04:33:41 2022 +0000 |
| tree | 2ccefc31fb06041a687128e3b0daced532227efa | |
| parent | e932fa83e37875a4aa1d6be2004f2d4b112fd06b [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/8812952745059654513 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/8ce3ab5d76932f1c40cffbbbe6f9bb7b47a47a07~..2f0d36b4a7a59a04abc8421edc9078205e3bab3f 8ce3ab5 (olivernewman@google.com) [fuchsia/build] Nest task request construction 0c9166b (ihuh@google.com) [coverage] Specify llvm-profdata by clang/rust type. 3d47eb4 (olivernewman@google.com) [testing_requests] Create requests in parallel 2f0d36b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/e52acbc0987bdb31369aba51894b98286a418582 e52acbc (andrewlamb@chromium.org) [recipes-py] roll recipe proto. 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: Ife1b51524ca1c9113197d27391ac28807d9115c0 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/96254 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Bot-Commit: 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.