commit | 2f7d4ba389ccd7d1c73d661f85fbdf1a88e529e4 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Fri Jul 01 05:04:11 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 01 05:04:11 2022 +0000 |
tree | c7787d64641702918723ae852f9facd37a3b5d32 | |
parent | 2fc2ba08ce7ac8eb785134ac26adc998eed10aec [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/8809870816442843985 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/c10989a246eecbd5b9a75b6adaf2422d07fdb8c7~..3f1b2e57864965e092d8b8dfb2a67b7d2210e734 c10989a (danikay@google.com) [disabled-tests] Improve regex to catch comments on re-enabling... 6918a3f (haowei@google.com) Use git from CIPD in Clang Windows build. 3f1b2e5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/fe626574f31049199406b9328f2e8ce9fba4693d fe62657 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 361f01c81b49 to d3fd72180a64 More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: If9f80e5ee6976623ebfe5c3ac4f47e2f3838112f Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/100645 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: Recipe Deps Roller <recipe-deps-roller@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.