commit | 9f914d32eb7a7e56933dbed51c9cd2e5c9f17c47 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri May 27 21:56:56 2022 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 27 21:56:56 2022 |
tree | 546beb9949adf23a9698b8b0af60ee15562afcc4 | |
parent | ac0a8cb24f9989a0bd6a08d43467e8a00431ac86 [diff] |
Roll chromiumos/infra/proto from aeaf5ce9088c to 505826b05d9e (1 revision) https://chromium.googlesource.com/chromiumos/infra/proto.git/+log/aeaf5ce9088c..505826b05d9e 2022-05-27 jackneus@google.com builder_config: Add PUBLIC as builder type If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-proto-infra-autoroll Please CC chromeos-continuous-integration-fire-hose@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: None Tbr: chromeos-continuous-integration-fire-hose@google.com Change-Id: Ib38d039537e0128fdcc45c94de5d386db6ecb26c Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/3673908 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#49375}
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.