|author||recipe-roller <email@example.com>||Wed Jan 12 06:52:40 2022 +0000|
|committer||CQ Bot Account <firstname.lastname@example.org>||Wed Jan 12 07:39:39 2022 +0000|
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/8825263165180409041 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/c03c9b3bdeab0fcc3f6d46681c16e90dfb66dc48~..adf999d0f7527b14bb01549c2e0c1b1e9ace4966 c03c9b3 (email@example.com) [roll] Update tools to latest c268846 (firstname.lastname@example.org) [testing_requests] Add nsjail-root to testrunner command. 00ac664 (email@example.com) [roll] Update tools to latest a49b7e0 (firstname.lastname@example.org) [autocorrelator] Use api.runtime.in_global_shutdown 6e7a43b (email@example.com) [roll] Update tools to latest 8dbe627 (firstname.lastname@example.org) Don't run steps during build shutdown 6c1ba2e (email@example.com) [roll] Update tools to latest adf999d (firstname.lastname@example.org) Add branch to checkout step and submodule update tool input recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/7ef38cec62e1193e9eaeb064add76798bb07019a 7ef38ce (email@example.com) [recipes.py] Don't silence `git fetch` stderr More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Rfirstname.lastname@example.org Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ib0dc1153e0ab0b2dab42b8a9e20fe8b1f484793e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/78200 Bot-Commit: Recipe Deps Roller <email@example.com> Commit-Queue: Recipe Deps Roller <firstname.lastname@example.org>
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.