commit | 48810a0e90cf48f01e6a1e23281246e5b20bf9c8 | [log] [tgz] |
---|---|---|
author | Josip Sokcevic <sokcevic@google.com> | Wed Mar 17 21:57:50 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 17 21:57:50 2021 |
tree | 2e18c8b273b6986b4347ab5224f7bc6b3f172a07 | |
parent | 235ec572e370971180b7a72d97a864dca18658ca [diff] |
Grant chops source permission to trigger cs builds It's useful to have an option to retrigger failed build. We may want to do that if the latest run failed and builder instance was replaced. Otherwise, we need to wait for next scheduled run, which may take 4 hours. Change-Id: I284d5a8b5ce85553892fd9957f3963099c5418ac Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2769621 Reviewed-by: Robbie Iannucci <iannucci@chromium.org> Commit-Queue: Josip Sokcevic <sokcevic@google.com> Cr-Commit-Position: refs/heads/master@{#39461}
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.