Google Git
Sign in
chromium / infra / infra.git / 53ab78708acb123a38b58b0322d80189ea680913
commit53ab78708acb123a38b58b0322d80189ea680913[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Apr 01 15:54:28 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Apr 01 15:54:28 2023
tree7dbfb3d81978db1002df07ea239a87153a01b5ce
parentee0e10e4fad182a60230f8a86c2a54ab095ab4a4 [diff]
Roll chromiumos/config from 19e31b21df85 to 79db297f83ac (1 revision)

https://chromium.googlesource.com/chromiumos/config.git/+log/19e31b21df85..79db297f83ac

2023-04-01 yulunchen@google.com Add keyboard backlight properties into hw_topology

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,andrewlamb@google.com,chromeos-infra-discuss@google.com,pprabhu+autoroll@google.com,pprabhu@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/main/autoroll/README.md

Tbr: andrewlamb+autoroll@google.com,pprabhu+autoroll@google.com
Change-Id: I92a6add1b2753a899d87a11b426db688b097c730
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/4391706
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/main@{#55837}
1 file changed
tree: 7dbfb3d81978db1002df07ea239a87153a01b5ce
  1. 3pp/
  2. appengine/
  3. appengine_module/
  4. bootstrap/
  5. build/
  6. chromeperf/
  7. cipd/
  8. crdx/
  9. doc/
  10. docker/
  11. go/
  12. infra/
  13. node/
  14. packages/
  15. python_pb2/
  16. recipes/
  17. test/
  18. utils/
  19. .gitallowed
  20. .gitattributes
  21. .gitignore
  22. .style.yapf
  23. .vpython
  24. .vpython3
  25. .yapfignore
  26. codereview.settings
  27. CONTRIBUTING.md
  28. DEPS
  29. LICENSE
  30. navbar.md
  31. OWNERS
  32. PRESUBMIT.py
  33. README.md
  34. run.py
  35. test.py
  36. WATCHLISTS
  37. WHITESPACE
README.md

infra.git repository

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.

Entry points

  • run.py: wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • test.py: multi-purpose script to run tests.
  • packages/infra_libs/: generally useful functions and classes
  • infra/services/: standalone programs intended to be run as daemons.
  • infra/tools: command-line tools, intended to be run by developers.
  • appengine/: many Chrome-infra-managed AppEngine applications.
  • infra/experimental: for, well, experimental stuff. Once they are stabilized and reviewed, they should be moved in a more permanent place.

Miscellaneous technical stuff

  • bootstrap/: utilities to set up a proper Python virtual environment.
  • infra/path_hacks: submodules of this modules give access to modules in the build/ repository. from infra.path_hacks.common import <stg> is actually getting <stg> from build/scripts/common.
  • utils/: purpose? utils?
  • Need to bump infra/deployed to pick up changes?
    • git push origin <updated hash>:deployed
    • mail chrome-troopers@, include:
      • previously deployed hash (for quick rollback)
      • the hash you just pushed
      • the list of CLs that made this push necessary
      • the output of the git push command

Integrating tests with test.py

If you've added a new module, run your tests with test.py:

  1. Create a .coveragerc file in the root directory of the module you want to test. Take a look at another .coveragerc to see what to include in that.
  2. Create a “test” directory in the root directory of the module you want to test. Move your *_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.

Style

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.