| commit | 630409a52d5a0a1d57d1727891fa8673a9e33b18 | [log] [tgz] |
|---|---|---|
| author | Oliver Newman <olivernewman@google.com> | Wed Sep 27 17:33:25 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 27 17:33:25 2023 +0000 |
| tree | c1897f6c5ee87e770b99185014c54b370c0e984f | |
| parent | d3d6382b6f22b60cdb3ea25cf3655cf9d582a0ba [diff] |
[environment] Use updated toolchain override mechanism https://fxrev.dev/892038 updated the mechanism by which fuchsia toolchain builders override the toolchain with a custom version, update Pigweed recipes accordingly. Note that this is not a stable interface and should ideally not be depended on outside the fuchsia recipes repo, Pigweed should not be depending on properties that are intended to only be read by a single fuchsia recipe module. Long-term I'd suggest updating the fuchsia recipe to set additional non-fuchsia-specific properties that can be read by Pigweed, something like a top-level "toolchain_overrides" property. Change-Id: Idd4e8daf56d28d222f7169a5f74f5a4c69de04dc Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/173110 Reviewed-by: Rob Mohr <mohrr@google.com> Pigweed-Auto-Submit: Oliver Newman <olivernewman@google.com> Commit-Queue: Auto-Submit <auto-submit@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.