commit | 7e9e1b509add1cd855e11f3da8c52b4fd38b012a | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Jan 08 14:08:15 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 08 14:08:15 2021 |
tree | e19924158e8f8f379b6f53cd24b385dd401901fd | |
parent | 980df363f8091769762e0355d9cb17deb213c7da [diff] |
Roll luci-py from fba6ecb56b6c to c6f62500f1dd (1 revision) https://chromium.googlesource.com/infra/luci/luci-py.git/+log/fba6ecb56b6c..c6f62500f1dd 2021-01-08 jmpittman@google.com Support Mac-${MAJOR}, Mac-${MAJOR}.${MINOR}, and Mac-${MAJOR}.${MINOR}.${PATCH} when reporting OS version. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/luci-py-infra-autoroll Please CC tikuta+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: tikuta+infra-roll@chromium.org Change-Id: Iafd2f595bba344fea12e73b033a53d6bb36123ae Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2616805 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@{#37423}
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.