commit | 73f801ee6ea44e2c48d524f71aaa0fa9421636df | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Fri Jun 03 23:09:30 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 03 23:43:37 2022 +0000 |
tree | a2354e7663e05950744961e29d66dc2017168ab6 | |
parent | cd47d1773eb8fd040af8c342687e0b49b79ab58d [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/8812336816792202321 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/552b70e852505958782c047813b440b79587bd03~..57b08a414cb2700822b3576e4fa86a360bc7c37d 552b70e (nmulcahey@google.com) [build/btu] Set XDG_*_HOME, HOME env vars f4b2edb (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest d770b63 (olivernewman@google.com) [fuchsia] Fail if no tests were run 370b270 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 57b08a4 (atyfto@google.com) [fuchsia] Add top-level property to filter Guitar tests 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: If77cf23a47cff3be043be2f3d6d4f6fb911095c5 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/96960 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Bot-Commit: 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.