commit | d9775fbace64400d965799359d4d519015c11726 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Dec 01 22:08:09 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 01 22:08:09 2020 |
tree | 3d6315012872d918d2429f1a46af46b47ddba189 | |
parent | e5f4fce9aa5f866d0150b318c0d17f6623df4f67 [diff] |
Roll luci-go from 20153f2c16f2 to 4295d1b0fd53 (2 revisions) https://chromium.googlesource.com/infra/luci/luci-go.git/+log/20153f2c16f2..4295d1b0fd53 2020-12-01 tandrii@google.com cv: implement poller state management. 2020-12-01 vadimsh@chromium.org [dscache] Implement Redis backend. 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: I9393e2a00d33dc16151b3d1c738d1196c5a0928b Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2568610 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@{#36807}
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.