|author||recipe-roller <email@example.com>||Mon Jan 24 06:55:24 2022 +0000|
|committer||CQ Bot Account <firstname.lastname@example.org>||Mon Jan 24 23:40:41 2022 +0000|
Roll recipe dependencies (nontrivial). 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/8824176004408380513 Please review the expectation changes, and LGTM+CQ. fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/f699e21ee94a07a0bbe713d31cfe517886977a3f f699e21 (email@example.com) [cache] Include cache name in guard file step names More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Rfirstname.lastname@example.org, email@example.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ib1c01685fc2f223db035d9d8768a8ce51ab03414 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/81180 Reviewed-by: Ted Pudlik <firstname.lastname@example.org> Commit-Queue: Ted Pudlik <email@example.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 .)
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
./black is present.