| commit | d5248de5a3ab2cf6ece2eeaf9855799f4ad7ba7d | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Jul 31 21:04:46 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 31 21:04:46 2023 +0000 |
| tree | ec298747d967329bc2b1a6749f9785f1db5135c9 | |
| parent | f5003a4f928eac00816c4a66e85d94c13c754c3a [diff] |
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/8774046572663261249 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/a6e974e734703ba4c0198734dabaf6216f357643~..e9e0416299aee3da88831fc772a25423fba8f143 a6e974e (phosek@google.com) [toolchain_trigger] Passthrough version to builders d272096 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools c0be64b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 5f999c1 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools bbc96c7 (phosek@google.com) [build] Fetch toolchains to location inside the checkout 8ccfff1 (mcgrathr@google.com) [clang_toolchain] Don't try to synthesize riscv64 in Fuchsia SDK 5acd30f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools e9e0416 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/c4b5574c585e5ca512dd768b4f6d43b6e2be5a3e c4b5574 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from ef429984e650 to 5421d411d439 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: I18090ff70fd3df0ecd1e8f8454e39fe08b28c126 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/161370 Commit-Queue: Rob Mohr <mohrr@google.com> Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.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 .).recipe_deps/fuchsia/scripts/cleanup_deps.py --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 ./scripts/ensure_black.sh before ./black is present.