commit | 9e490cee84f8daad145a7147c312cfbb07cb16b3 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Mar 31 00:18:58 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 31 00:18:58 2021 |
tree | f6b04420750e6aef8e76f3e55de2d21eb3f56f61 | |
parent | 4b051262253462edb278772b87852caed6c4c89a [diff] |
Roll chromiumos/infra/proto from a16a27087c80 to 560cfe407a20 (1 revision) https://chromium.googlesource.com/chromiumos/infra/proto.git/+log/a16a27087c80..560cfe407a20 2021-03-31 lamontjones@chromium.org builder_configs: drop id.branch 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: None Tbr: chromeos-continuous-integration-fire-hose@google.com Change-Id: I466aa8282ecbd9a1f9564bc8c64a2588afd87de5 Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2796096 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@{#39796}
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.