|author||recipe-roller <email@example.com>||Thu Nov 24 01:15:27 2022 +0000|
|committer||CQ Bot Account <firstname.lastname@example.org>||Thu Nov 24 01:15:27 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/8796659021204533473 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/5947323024d64334dab3ad4688d456becc61b293~..bf84359a64c4d4fda1e38c78e49a7e33219a8008 5947323 (email@example.com) [clang_ml_training] Train in a single recipe run 599f8b1 (firstname.lastname@example.org) [roll] Update tools to latest d35df32 (email@example.com) [roll] Update tools to latest bf84359 (firstname.lastname@example.org) [testing_request] Remove testrunner from botanist command recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/189a0bb4a1d2f670f0a1c72d9d616bd36bfb4d63 189a0bb (email@example.com) [bcid] Uprev provenance broker tool. Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I361550ff760ba7ee1658acac8dcdf88a1975ab23 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/121016 Commit-Queue: Recipe Deps Roller <firstname.lastname@example.org> Bot-Commit: Recipe Deps Roller <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.