commit | 9a18c0fc6b80fb7e1f5dbda217c916f6851a0bdf | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Apr 13 19:23:37 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 13 19:23:37 2021 |
tree | 2baa574da386939e41dcbf491b141b255ebe750d | |
parent | 35bb7ebb67a015d057297da57ec8132c19ccdb40 [diff] |
Roll chromiumos/infra/proto from f8d2f6cc7f35 to 1ad13106c71a (1 revision) https://chromium.googlesource.com/chromiumos/infra/proto.git/+log/f8d2f6cc7f35..1ad13106c71a 2021-04-13 engeg@google.com pointless: add relevance to known non portage paths 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:1198619 Tbr: chromeos-continuous-integration-fire-hose@google.com Change-Id: I784dcb0d64985a97e3a14963138821a406a15c54 Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2822861 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#40121}
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.