| commit | fbf876cc26cd3f8f5e5d5b11a84a642995c12f25 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Fri May 05 19:21:34 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 05 19:21:34 2023 +0000 |
| tree | 12c00583a67d13f319d96caa7bc71eac45139aaf | |
| parent | cdbcd08b8dbcce12e2ff72d0923bd9eede998fc8 [diff] |
environment: Move envtest log saving logic here Move logic about saving environment log files to the environment module, where it can be used by that module and by the envtest recipe. Change-Id: Ie8a0798d8bedb3b128fc5d9cc192fbceba8eae84 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/145250 Reviewed-by: Oliver Newman <olivernewman@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: Auto-Submit <auto-submit@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.