commit | 13826bc9c61f119d2999d40bbf4f5d9f58c98db3 | [log] [tgz] |
---|---|---|
author | Eshwar Narayan <eshwarn@google.com> | Wed Apr 07 01:20:39 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 07 01:20:39 2021 |
tree | 6a5a448121d377243dffec3d1d7bf1f73b0d7ad7 | |
parent | a342afdd668997e73fb78fdba3db29a915ba7f00 [diff] |
shivas: add cmd for schedulingunit Bug: b/180138776 Test: run local coammnd against ufs-dev; ./shivas add schedulingunit -name sc-1 -duts chromeos6-row22-rack13-host1,chromeos6-row22-rack13-host5 -pools DUT_QUOTA,HTL -tags "first sc" -type all { "name": "sc-1", "machineLSEs": [ "chromeos6-row22-rack13-host1", "chromeos6-row22-rack13-host5" ], "pools": [ "DUT_QUOTA", "HTL" ], "type": "SCHEDULING_UNIT_TYPE_ALL", "description": "", "updateTime": "2021-04-05T18:58:28.552302321Z", "tags": [ "first sc" ] } Successfully added the SchedulingUnit sc-1 Change-Id: Ia1b4fc5e7f0e160619566d61b8f58f2011ade01b Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2805624 Commit-Queue: Eshwar Narayan <eshwarn@chromium.org> Reviewed-by: Garry Wang <xianuowang@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#39972}
Testing Welcome to the Chrome Infra repository!
Wondering where to start? Check out General Chrome Infrastructure documentation. In particular, to check out this repo and the rest of the infrastructure code, follow the instructions here. The rest of this page is specific to this repo.
sys.path
modifications.from infra.path_hacks.common import <stg>
is actually getting <stg>
from build/scripts/common.git push origin <updated hash>:deployed
git push
commandIf you've added a new module, run your tests with test.py:
*_test.py
files to this directory.Double-check that your tests are getting picked up when you want them to be: ./test.py test <path-to-package>
.
Tests still not getting picked up by test.py? Double-check to make sure you have __init__.py
files in each directory of your module so Python recognizes it as a package.
The preferred style is PEP8 with two-space indent; that is, the Chromium Python style, except functions use lowercase_with_underscores
. Use yapf (git cl format
) to autoformat new code.