commit | 71526ea5ff7e95d8b8165541a1c4ebf218735799 | [log] [tgz] |
---|---|---|
author | Josip Sokcevic <sokcevic@google.com> | Mon Dec 07 23:18:17 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 07 23:18:17 2020 |
tree | 1a1bef3b8fb3d7307e4401919ccc732c628cbf3d | |
parent | 05539a3435b820665ee609b9712c2001a7c2fb90 [diff] |
Use new-branch in recipe autoroller This will resolve to default branch of local git workspace. It may be different from remote for older clones. Bug: 1155492 Change-Id: I1fa265a5075944859de64403577b95a261fdeb0d Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2577602 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Cr-Commit-Position: refs/heads/master@{#36943}
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.