Google Git
Sign in
chromium / experimental / codesearch / infra / infra / 22a08ac4f6eeb4a3b79046a07667fd4bdac8e668
commit22a08ac4f6eeb4a3b79046a07667fd4bdac8e668[log] [tgz]
authorOwen Rodley <orodley@chromium.org>Mon Jan 14 02:44:09 2019
committerCommit Bot <commit-bot@chromium.org>Mon Jan 14 02:44:09 2019
treea5773bb8e9fc8dae2fa4cf980fe33e24488cd58a
parentbb36d9fac197879a94032e65b229fb8bb94dd728 [diff]
Add a branch for the latest non-synthetic commit.

Bug: 894279
Change-Id: Ibbfc1ed907faf29aa24f4c9065105e3a3596da67
Reviewed-on: https://chromium-review.googlesource.com/c/1408668
Commit-Queue: Owen Rodley <orodley@chromium.org>
Reviewed-by: Joey Scarr <jsca@chromium.org>
Cr-Commit-Position: refs/heads/master@{#19958}
Cr-Mirrored-Commit: 3a00203029a31509cfb37428e74b0a847bb4e69d
4 files changed
tree: a5773bb8e9fc8dae2fa4cf980fe33e24488cd58a
  1. 3pp/
  2. appengine/
  3. appengine_module/
  4. bootstrap/
  5. build/
  6. cipd/
  7. crdx/
  8. data/
  9. doc/
  10. docker/
  11. glyco/
  12. go/
  13. infra/
  14. node/
  15. packages/
  16. recipes/
  17. test/
  18. utils/
  19. luci
  20. recipes-py
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. navbar.md
  29. OWNERS
  30. PRESUBMIT.py
  31. README.md
  32. run.py
  33. test.py
  34. WATCHLISTS
  35. 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.
  • 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, integrate 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. More 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.