Roll infra/luci/ 851d2d0d1..4cc258d5e (5 commits)

$ git log 851d2d0d1..4cc258d5e --date=short --no-merges --format='%ad %ae %s'
2019-05-23 smut [components] Restore gce module
2019-05-23 vadimsh [auth] Add protos for "store signed AuthDB snapshots in GS" feature.
2019-05-22 crouleau [Swarming Client] Print links to tasks after they are triggered.
2019-05-22 maruel [client] Enable specifying containment-type for trigger
2019-05-21 smut [swarming] Remove setting/handling of MP-related properties

Created with:
  roll-dep infra/luci


Change-Id: I4dd47e7b88a1a2a668db32b554c17e24a5f368fb
Auto-Submit: Andrii Shyshkalov <>
Commit-Queue: smut <>
Reviewed-by: smut <>
Cr-Commit-Position: refs/heads/master@{#23204}
1 file changed
tree: abf76163e3495513548aafcbc87772a5f18a29fb
  1. .gitattributes
  2. .gitignore
  3. 3pp/
  5. DEPS
  12. appengine/
  13. appengine_module/
  14. bootstrap/
  15. build/
  16. cipd/
  17. codereview.settings
  18. crdx/
  19. data/
  20. doc/
  21. docker/
  22. glyco/
  23. go/
  24. infra/
  26. node/
  27. packages/
  28. recipes/
  31. test/
  32. utils/

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

  • wrapper script to run programs contained in subdirectories without having to deal with sys.path modifications.
  • 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

If you've added a new module, integrate your tests with

  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 * files to this directory.

Double-check that your tests are getting picked up when you want them to be: ./ test <path-to-package>.

Tests still not getting picked up by Double-check to make sure you have files in each directory of your module so Python recognizes it as a package.