commit | 942e6e759939f82f5c3f985caa954ac0e228e026 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Mon Dec 20 22:33:49 2021 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 21 00:06:04 2021 +0000 |
tree | 066fba17dcfb2eb4caaa9e3cc26cecce022f9ea6 | |
parent | 663e8e6508158644d63768191c119f2e00cd3308 [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/8827287590344271537 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/6cd1a5ec546c47f7e1d6a061ce1b65aca4aa2fbc~..be12f47ca389477fdba5b56b137654e100c82f8f 6cd1a5e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest be12f47 (jessicacgu@google.com) [fxt] Update recipes fuchsia (image) to trigger Guitar project recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/66937e22dd960f3c09d0becf7e15149a360d2cb0 66937e2 (iannucci@chromium.org) Add placeholder recipe for help with UI integration experiments. 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: I09c4ffff3599baa9c945a0e8edfe86f5b0a8e3b4 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/75800 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@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.