commit | 2ce93791cd8e8aa07bbafdaae8bdd5aaaa677f5f | [log] [tgz] |
---|---|---|
author | Garrett Beaty <gbeaty@chromium.org> | Sat Nov 07 01:00:40 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Nov 07 01:00:40 2020 |
tree | 982bd00a89640d05f6ee9db002639180ce9e0db9 | |
parent | 19e2218a58c03100613c886e579d3c4ef94dcfa2 [diff] |
Create test-type-specific spec types. Having separate spec types for each test allows for a reliable comparison to be performed between specs created in recipes and specs created from the source side spec files since the specs implement equality by virtue of being attrs-based classes and any default logic is handled in the creation of the specs. Bug: 1128746 Change-Id: I33a193fa612724e85ee9f3803fd71c2f84f7ef44 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/build/+/2518342 Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Reviewed-by: Stephen Martinis <martiniss@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.