commit | 74fb5861134ce3e1c450eaf331aecb7435de9df0 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Mon Dec 13 22:55:43 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 14 00:16:24 2021 +0000 |
tree | f1dab1fd9c6d30af4d7d7fa6faef0b946828e7c1 | |
parent | 2b02aadd95aba6294f8447604ba1e29dd42709de [diff] |
Roll recipe dependencies (trivial). 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/8827920930225549969 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/a9d401edc72289a63a6e5eac87e637fcf62e5621~..0d666c0ba8fd17411357b474a0f438657b826a2e a9d401e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 3283967 (olivernewman@google.com) [recipe_testing] Set recipe_testing props on BB subbuilds ac28888 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 0d666c0 (yuanzhi@google.com) [femu] Update Android target to CIPD map. More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Id8769230edebf4e6f00492fe308fc3053c47c58a Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/74002 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> Reviewed-by: 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.