commit | 7d2f42ec900ec6753a5ddb9f63eb68a2d837407b | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Mon Mar 21 06:51:57 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 21 19:08:32 2022 +0000 |
tree | 10b8f9b34a544e47113036d3ab2cb2c674a57bf7 | |
parent | 82904c1e34a170770b13949de83c9053d2526c0e [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/8819102573077872145 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/0b45996fb9db0aaeb75dbd1181885aedddff2894~..b433eea98387f9cf52e326ec399146c5f0ad9eca 0b45996 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 31c7039 (phosek@google.com) [clang_toolchain] Handle lld flag correctly 0820932 (olivernewman@google.com) [build] Turn red if duplicate tool encountered 06f8405 (atyfto@google.com) [size] Rename "size_diff" module to "binary_size" 03b6b34 (atyfto@google.com) [binary_size] Integrate size_check tool for budgets 493f906 (atyfto@google.com) [build] Run budget check tool post-build b92cc78 (joshuaseaton@google.com) [qemu] Remove pre-v6.2 codepaths 0cc71dc (joshuaseaton@google.com) [qemu] Rename expectation test names 64181f0 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest e161412 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 1313a8a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 8a0ffcc (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest b0b82e9 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 53ad556 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 16a2cbe (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6d7d99d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest b433eea (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I14d08fa235f089c6840b18587eaf21c26f298f16 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/88710 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Reviewed-by: Rob Mohr <mohrr@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.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.