commit | 89195e03f3314d1f8efc4644aa0640abad4ab6be | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Apr 15 00:36:00 2021 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 15 00:36:00 2021 |
tree | 0d2fe25356c7c3e07c6f49bc66310e5d2e56cba7 | |
parent | c2525cb871aced770260ed33181ec8f0cb71d184 [diff] |
Roll chromiumos/config from 320f71d5c742 to 1d010e096215 (1 revision) https://chromium.googlesource.com/chromiumos/config.git/+log/320f71d5c742..1d010e096215 2021-04-15 smcallis@google.com boxster: generate flattened entry even if no design config defined. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromiumos-config-infra-autoroll Please CC andrewlamb+autoroll@google.com,pprabhu+autoroll@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 Tbr: andrewlamb+autoroll@google.com,pprabhu+autoroll@google.com Change-Id: Ifaef9fcfc0e83a40d4774904e6b0bf1a8304c49a Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2826813 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@{#40174}
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.