commit | b82474dea5ffe9be376621838030d832f0bee004 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Wed Jun 08 03:35:27 2022 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 08 13:59:10 2022 +0000 |
tree | a896248689bbbf0a9bda134626a50da75469153d | |
parent | bf59c6e658075d40d5225d10bb2355f706712ec9 [diff] |
pw_presubmit: Log timeout for steps The timeout is already in 'execution details', but there we're given a start time for the step and the deadline time (by which the step must complete). Since I'm often looking at the duration of the step in MILO, add a step showing the timeout as a duration just before launching the actual step. Change-Id: Icdd219970626645680aefbb002e4125e2d72c5b3 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/97387 Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Oliver Newman <olivernewman@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.