Google Git
Sign in
chromium / infra / infra / bd98d2d7255f
commitbd98d2d7255f400ffda08cfaa4e2f196e8149346[log] [tgz]
authorrecipe-roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>Sat Sep 19 00:42:35 2020
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Sep 19 00:42:35 2020
tree6f84b0b3b86685fa098e060b726004862042586c
parentc25dfdada56f0eab1bba64cb3b68311727e5e8f9 [diff]
Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (build) into this repository.

build:
https://chromium.googlesource.com/chromium/tools/build.git/+/d4c999e13365a6a091f546977f012b97dbd9a558
  d4c999e (dpranke@google.com)
      Make LocalIsolatedScriptTests() work w/ raw commands.

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.

TBR=iannucci@chromium.org

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Id8728c625dea11e2d7e34030b54575c70e53a952
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2419891
Reviewed-by: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Recipe Roller <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#35216}
2 files changed
tree: 6f84b0b3b86685fa098e060b726004862042586c
  1. .gitattributes
  2. .gitignore
  3. .style.yapf
  4. .yapfignore
  5. 3pp/
  6. CONTRIBUTING.md
  7. DEPS
  8. LICENSE
  9. OWNERS
  10. PRESUBMIT.py
  11. README.md
  12. WATCHLISTS
  13. WHITESPACE
  14. appengine/
  15. appengine_module/
  16. bootstrap/
  17. build/
  18. chromeperf/
  19. cipd/
  20. codereview.settings
  21. crdx/
  22. doc/
  23. docker/
  24. glyco/
  25. go/
  26. infra/
  27. navbar.md
  28. node/
  29. packages/
  30. python_pb2/
  31. recipes/
  32. run.py
  33. test.py
  34. test/
  35. utils/
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.