| commit | 019a488bcb6494e76b8dc0cc6199674771b062a7 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Aug 29 01:14:48 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 29 01:14:48 2023 +0000 |
| tree | 2fe1d25e829a9685cb7638fdcd9638be2aba8526 | |
| parent | 632fd0acaef4ac41d2f11890e2db6e0a6900a590 [diff] |
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/8771473135410387793 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/21b4273282b844f4fa07d4b12dd8c1058c1284f4~..ce0f6e0f4ed91df875f6b25cc84489cbe73b27eb 21b4273 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools ba1b8fc (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 4aaea31 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 87a1cc5 (olivernewman@google.com) [shac] Set CIPD log level to "error" 014926a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 8efce39 (dkoloski@google.com) [rust] Add stripped binaries to CIPD packages 8bd2e79 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools b194835 (olivernewman@google.com) [gerrit_auto_submit] Expand retry logic comment 1e5c364 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 536a629 (tmandry@google.com) [rust_toolchain] Add a "channel" property d5191a3 (tmandry@google.com) [rust_toolchain] Fix bootstrapping with an upstream compiler 2083752 (chaselatta@google.com) [bazel] turn off bazel cc autoconfiguration c87f564 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 90dc414 (dthorn@google.com) [Clang] Break LLDB build dependency on gcc/binutils ce0f6e0 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 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: Ib6ae2450f61c4f6993e72b9390c20dd0197b7645 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/168757 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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.