commit | 98cb0022b0e4f2c6b05a23b31bfe532ed9924885 | [log] [tgz] |
---|---|---|
author | Dirk Pranke <dpranke@google.com> | Wed Sep 23 23:58:14 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 23 23:58:14 2020 |
tree | 11909777c262f0ead1871dbf38f4e41602c8be80 | |
parent | e682da1f7b9033743cd7ad7f992dfdd8f436aad5 [diff] |
Remove --isolated-script-test-perf-output from chromium recipe. As discovered/discussed in crbug.com/1127545, it appears that this flag is not actually ever used anywhere in the chromium recipes. Perf tests *do* produce output, but they don't use this flag to do so. WebRTC tests *do* use this flag, but they set this directly in their own recipes. Bug: 1127545 Change-Id: I215ad8f698c18e41ca2a87c7043371a9ac73000b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2427305 Reviewed-by: Stephen Martinis <martiniss@chromium.org> Commit-Queue: Dirk Pranke <dpranke@google.com>
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.