| commit | 0c74d9ee9b937740c6dcb48ba3b5c42f50e4163a | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Mon Apr 25 06:51:35 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 25 21:44:12 2022 +0000 |
| tree | e87937daa23ce684c5bf9cbfbe49a078109b7134 | |
| parent | e4bcd2219e91360f880a11bbb40b0010cd7ab7f2 [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/8815931680420275761 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/497529fced3c4234e2207bd9e7aa28da2643e8f1~..aff1fc29c3c7a0735717ddcbcdcb1c9a5349228a 497529f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest c446894 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6230ced (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 694511c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest b00f027 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 25245b5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 7a315b3 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest e8e6787 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 002c0aa (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 918eff3 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 7f716e7 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest aff1fc2 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/efaa1e2e3e663d5342ed58bd3fdfc8cde25b6cee~..dc013a866f2fd28bccdc390f259995e1004dcdf1 efaa1e2 (iannucci@chromium.org) [json] Stop using python.inline. dc013a8 (iannucci@chromium.org) [python] Mark python.inline with a warning 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 Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I0b42d0b954add6246efda4e069c2d3ca15c255ab Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/92364 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.