| commit | 325823c861fca6d583a562bb9481dcc0f35e0322 | [log] [tgz] |
|---|---|---|
| author | Yiwei Zhang <yiwzhang@google.com> | Wed Jul 14 18:01:39 2021 |
| committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 14 18:01:39 2021 |
| tree | fff2ab5cec004d0876dcf6235c110d99d69850e7 | |
| parent | 6254729dfa2e618742f04f3240e2f2483ebc25b5 [diff] |
Revert "Support running different py version simulation recipe tests" This reverts commit a99dd7a5b4632d294b95ff0c84928011bffb59e7. Reason for revert: causing https://crbug.com/1229240 Original change's description: > Support running different py version simulation recipe tests > > 1. Have two pools to run py2 and py3 _runner subprocesses respectively. > 2. Add a new `incompat_py_support` field in the test Outcome message. > 3. The main process will use the `incompat_py_support` to decide to > treat it as a real failure or not when returning exit code. > > Bug: 1211651 > Change-Id: I7e01740f3b9a648f540a71127a098fdbdaa0ad9c > Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/2988363 > Commit-Queue: Yuanjun Huang <yuanjunh@google.com> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Bug: 1211651 Change-Id: Iac6c06749d792f5ee204b4fafa0ae23c72521afe Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/3027200 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Yiwei Zhang <yiwzhang@google.com> Reviewed-by: Scott Lee <ddoman@chromium.org> Commit-Queue: Yiwei Zhang <yiwzhang@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.