| commit | 62ca441e14052ee3cc4d75e8abaeda61ce7ffe67 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Thu Apr 18 18:43:03 2024 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 18 18:43:03 2024 |
| tree | f1515a86a790065b1d8d86df6e5b6272f433f9b4 | |
| parent | 2d4b5456534f32afc385663a5395273759009f18 [diff] |
[commands/test] Add warnings for long-running tests Add output to './recipes.py test train' and './recipes.py test run' that shows any tests that took longer than 10s to complete. Test duration depends on many things and may not perfectly correlate to how much work was done in the test, but with this relatively high threshold it should clearly indicate tests that are probably doing something wrong. Change-Id: I4b01256ce6b65e36689132658165f0469b3a6657 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/5465200 Reviewed-by: Benjamin Shai <bshai@google.com> Reviewed-by: Chan Li <chanli@chromium.org> Commit-Queue: Rob Mohr <mohrr@google.com>
Recipes are a domain-specific language (embedded in Python) for specifying sequences of subprocess calls in a cross-platform and testable way.
They allow writing build flows which integrate with the rest of LUCI.
Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.
user.email and user.name are configured in git config.Run the following to setup the code review tool and create your first review:
# Get `depot_tools` in $PATH if you don't have it git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git $HOME/src/depot_tools export PATH="$PATH:$HOME/src/depot_tools" # Check out the recipe engine repo git clone https://chromium.googlesource.com/infra/luci/recipes-py $HOME/src/recipes-py # make your change cd $HOME/src/recipes-py git new-branch cool_feature # hack hack git commit -a -m "This is awesome" # This will ask for your Google Account credentials. git cl upload -s -r joe@example.com # Wait for approval over email. # Click "Submit to CQ" button or ask reviewer to do it for you. # Wait for the change to be tested and landed automatically.
Use git cl help and git cl help <cmd> for more details.