commit | e0186b98edf85946a4cda646a14a4e27bc5cb8bf | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Apr 14 04:08:51 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 14 04:08:51 2021 |
tree | 18c3e582f242e17ecb87e1dccb16abbd573fcd36 | |
parent | 458f2657546885bd89c1df9c0c998ed228ccb775 [diff] |
Roll luci-go from 71d2c51476cc to 6e8173c62a27 (2 revisions) https://chromium.googlesource.com/infra/luci/luci-go.git/+log/71d2c51476cc..6e8173c62a27 2021-04-14 weiweilin@google.com [resultui] render task ID in result entry header 2021-04-14 weiweilin@google.com [resultui] clean up test_loader.ts If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/luci-go-infra-autoroll Please CC tandrii+infra-roll@chromium.org 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 Tbr: tandrii+infra-roll@chromium.org Change-Id: I03de8f0e7338fc8d80b87717739be20114683b31 Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2825108 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@{#40151}
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.