| commit | 86c40f5f8710b6f6ad7af007ae81770978334119 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Wed Sep 28 15:10:39 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 28 15:10:39 2022 +0000 |
| tree | 3c2276d5312e1e2397e3cbaa784d876336fc0dbc | |
| parent | 4a778e35a1b96187fe66f94da1ea543adfd477bf [diff] |
build: Add timeouts to ninja calls Change-Id: I416ea86086aa0497d77baffadef44c0cdf7dee53 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/112113 Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Rob Mohr <mohrr@google.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.