| commit | e15cecbc906eef0583e364eeaeef4fd2b4352e6f | [log] [tgz] |
|---|---|---|
| author | Yiwei Zhang <yiwzhang@google.com> | Sat Mar 07 06:19:11 2020 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Mar 07 06:19:11 2020 |
| tree | 8dc80234655fda33b7b3404be597c7dfc006ad84 | |
| parent | 0e747474f9f9d02568598aec9070c361cd057163 [diff] |
Profile memory before every step execution if enabled in properties
Details:
* Add Pympler to vpython spec
* Define new proto for engine property and make it available in recipe
engine
* Print memory summary diff to 'debug' stream right before every step
execution
R=garymm, iannucci
Bug: 1057203
Change-Id: I118286e5d342b13908a5d31e760cf00266040366
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2080922
Commit-Queue: Yiwei Zhang <yiwzhang@google.com>
Reviewed-by: Robbie Iannucci <iannucci@chromium.org>
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.