commit | b3c2f2221ed86beb23b7ee2455a6f4fced563bfb | [log] [tgz] |
---|---|---|
author | Patrick Meiring <meiring@google.com> | Mon Apr 19 03:28:06 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 19 03:28:06 2021 |
tree | ad9fe34a1b0573dec84dd38f59d2b63f9b6dc3c1 | |
parent | 31a4144137d33772f7ded15e54cabad2dea4e560 [diff] |
tls: phosphorus: use BackgroundTLS in build-parallels-image-provision. Minimise differences compared to use of TLS in prejob to reduce chance of bugs being introduced. BUG=chromium:1193349 TEST=None Change-Id: I3ec2a815b71022d67507e049f0c2c2d33164c07a Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2823192 Commit-Queue: Patrick Meiring <meiring@google.com> Reviewed-by: Jack Neus <jackneus@google.com> Cr-Commit-Position: refs/heads/master@{#40223}
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.