commit | 751a3f73d0017532f11fcf3ef2faeacd6eeba3a0 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue May 10 18:35:37 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 10 19:09:22 2022 +0000 |
tree | 1fecf37d3ed532b795c9a20118003cec7460f6ee | |
parent | 3e59259fec147da1983f8a832f509735ef9dcc89 [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/8814528676250702673 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/ec2cc277f31e73572d3fb14a1144489aa29c4269~..68d494f3783692b28454f4d8b2d73340021d1b93 ec2cc27 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest eb9a94c (olivernewman@google.com) [dpi] Disable auto-rolls of DPI tool 9ad245d (atyfto@google.com) [btu] Add placeholder proto field gcs_manifest_command 445b595 (atyfto@google.com) [artifacts] Integrate gcs-util up subcommand 68d494f (atyfto@google.com) [btu] Enable uploads from GCS manifests 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: I578b3bf4a8f5ae8255bb44234a527f871301e1a8 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/94089 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.