|author||recipe-roller <firstname.lastname@example.org>||Mon Jan 23 22:35:04 2023 +0000|
|committer||CQ Bot Account <email@example.com>||Mon Jan 23 22:35:04 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) into this repository. The build that created this CL was https://ci.chromium.org/b/8791143185609074401 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/40a36a7a72491ef09d5e5275a91456ba2bf582d4~..44d4062f22109b7df3ed6f9481cf0f9be32b0274 40a36a7 (firstname.lastname@example.org) [testing_requests] Upload files directly from build dir 48f2f38 (email@example.com) [roll] Update tools to latest 1b3e35c (firstname.lastname@example.org) [roll] Update tools to latest 60882bc (email@example.com) [roll] Update tools to latest 44d4062 (firstname.lastname@example.org) [clang_toolchain] Replace CMakeError.log with CMakeConfigureLog... 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: I1343ca822d2c65354d6001540962956204b249ad Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/126816 Commit-Queue: Recipe Deps Roller <email@example.com> Bot-Commit: 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.