| commit | da932f275e46f0530f134a7d10bb444879ea42ea | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue May 24 09:19:09 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 24 10:55:50 2022 +0000 |
| tree | 59ff56a0a12bf4e81167ba918a6f63ca833bee67 | |
| parent | b14b8b87a3f780fb2ba39f87c68ab668656372b5 [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/8813295020617863313 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/4a3c3a26d6ae67d875fdbbeb20560a3013efa485~..104b49c267fd1437259a010902bd07e924230682 4a3c3a2 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 104b49c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/1caa943e0c00281cc2901a63b18fa34a988c0825~..80a446c361907cadba554956fa30275ad03341ac 1caa943 (bpastene@chromium.org) context: Correct misleading comment about inspect the recipe env 80a446c (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from e6630cac546f to a80cc32b1739 More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I927ec1cae8f331f4a11fe1f0e01d1e431a2044e1 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/95762 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.