| commit | 80bd31dcae574104b538ba5060ba55454f2e1529 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Mar 15 06:50:50 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 15 07:55:50 2022 +0000 |
| tree | 3ac3107836eb479906cf784b540310e001b21807 | |
| parent | 8543e717aaea8d304ed542cbd8e33b7a3fe649bd [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/8819646155939166705 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/75e36094647f4972b9f76c8e718ef56c5f2a6736~..4e8e15b662b843fdc7163747567eb438e181b194 75e3609 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest a6dd3b4 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 3aa8bb9 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 1593aa0 (olivernewman@google.com) [recipe_tools_roller] Include rolled tools in commit msg 29d038d (olivernewman@google.com) [test_owners] Include gn label in output JSON b667c2e (felizardo@google.com) [packer][salt] Fixes roller for packer base images 27a0dc8 (joshuaseaton@google.com) [qemu] Add support for specifying a tag instead of a branch 9ed064e (lijiaming@google.com) Add recipe module for dpi fetch b8435e9 (haowei@google.com) [clang] Fix cmake compatibility issue on mac 81912bb (mcgrathr@google.com) [binutils] Point python-config-wrapper at 3.8 c176510 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest d0ec3e1 (mcgrathr@google.com) [binutils] Use explicit /usr/bin/python3 on Mac d76201a (yupingz@google.com) [submodule_update] Add no_commit tag to integration_update 1204e1f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 5358a7d (joshuaseaton@google.com) [qemu] Complete transition from `branch` to `refs` 1ab9b06 (felizardo@google.com) [salt][packer] Fixes project id for packer image roller. eb77582 (felizardo@google.com) Revert "[salt][packer] Fixes project id for packer image roller." 4e8e15b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 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: I2341c9253df1aae15c6b1d623aaf774fdefffc8c Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/88241 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.