commit | 2ed02e49e6b5921d9553d9e0fea74d4e073c1ef2 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Dec 14 00:36:35 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Dec 14 00:36:35 2020 |
tree | 63f7124790299b1a53aa1361e6dfb6b5d1dac7d3 | |
parent | 466fba75899238cbc0467ff28da31bc7488bbe15 [diff] |
Roll chromiumos/infra/proto from 8767fcc47960 to 96e2e7fe3790 (1 revision) https://chromium.googlesource.com/chromiumos/infra/proto.git/+log/8767fcc47960..96e2e7fe3790 2020-12-14 meiring@google.com Add protobufs for commands used by build_parallels_image 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/master/autoroll/README.md Bug: chromium:1105967 Tbr: chromeos-continuous-integration-fire-hose@google.com Change-Id: I476a6138849a31de14d1127fe582cf8bccc1d435 Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2588993 Reviewed-by: 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/master@{#37062}
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.