Google Git
Sign in
chromium / infra / infra.git / bcc104645e228340068f2ef38c05cb2f2bb9b124
commitbcc104645e228340068f2ef38c05cb2f2bb9b124[log] [tgz]
authorimages-pins-roller <images-pins-roller@chops-service-accounts.iam.gserviceaccount.com>Sat Mar 25 00:56:07 2023
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Mar 25 00:56:07 2023
treee1d3433cb59063d86aaeb6ac19b1333070bf398e
parentfac87ac125c4bc1a8f8c853ce636915675d7e746 [diff]
[images] Roll pinned docker image tags.

Updated pins:
  * docker.io/library/debian:bookworm-slim

R=vadimsh@chromium.org

Change-Id: I927ba832982d19b358fea00879f90e6312abc83d
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/4371020
Commit-Queue: Images Pins Roller <images-pins-roller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Images Pins Roller <images-pins-roller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/main@{#55668}
1 file changed
tree: e1d3433cb59063d86aaeb6ac19b1333070bf398e
  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.