|author||recipe-roller <firstname.lastname@example.org>||Fri Jan 20 04:04:15 2023 +0000|
|committer||CQ Bot Account <email@example.com>||Fri Jan 20 04:04:15 2023 +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/8791484492934475809 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/1e348d4b39015ece147ad6d6120b094ed19ebffd~..9493be5bef612b18203c1ec0095abc70a9d2002c 1e348d4 (firstname.lastname@example.org) [bazel][sdk] Fetch and merge Bazel SDK and release to CIPD 9493be5 (email@example.com) [cipd_with_dependencies_roller] Add roll_options property. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/7ec46d46ce021b3b17526c5eb7a6492d385a02ea 7ec46d4 (firstname.lastname@example.org) Roll CAS Client from ff9307900bad to 8e7b251208a2 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: If2d2c24f8f968f3a942d1a909d58f54f23362125 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/126783 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.