commit | 5bef4b10b699e5a962b4c5176f93822124104646 | [log] [tgz] |
---|---|---|
author | Zhaoyang Li <zhaoyangli@chromium.org> | Fri Nov 06 23:50:40 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Nov 06 23:50:40 2020 |
tree | 450acec57757955da4b1555e1d9f99e7d483b1dc | |
parent | 10d72ac2e224e9e815eb027862ed6099e84764dd [diff] |
[code coverage] Add a succeeding_step when return in processing. When return during an expected processing logic, present a step in UI so folks know what caused returning. Currently when returns from here no processing coverage related info is presented. Bug: None Change-Id: Ic035a8afc8431ea36a862892f63c4b559bec5d5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2522707 Reviewed-by: Prakhar Asthana <pasthana@google.com> Reviewed-by: Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
If you're here to make a change to ‘recipes’ (the code located in scripts/slave/recipes*
), please take a look at the README for more information pertaining to recipes.
The preferred style is PEP8 with two-space indent; that is, the Chromium Python style. Functions use lowercase_with_underscores
, with the exception of the special functions RunSteps
and RunTests
in recipes. Use yapf (git cl format --no-clang-format
) to autoformat new code.