Google Git
Sign in
chromium / infra / infra / 2c693a91e1c02358a69aeef8922e47eae2a01ca9
commit2c693a91e1c02358a69aeef8922e47eae2a01ca9[log] [tgz]
authorPrathmesh Prabhu <pprabhu@chromium.org>Thu Dec 06 21:41:44 2018
committerCommit Bot <commit-bot@chromium.org>Thu Dec 06 21:41:44 2018
tree9ebd342c6ae7e4c21407270bfbde93aa26c6b52f
parenteecfeb32a546b9ff56044cd22099c3c8ff6ebe7b [diff]
Roll infra/go/src/go.chromium.org/luci/ 1a51c20bc..9d3688949 (6 commits)

https://chromium.googlesource.com/infra/luci/luci-go/+log/1a51c20bc545..9d3688949727

$ git log 1a51c20bc..9d3688949 --date=short --no-merges --format='%ad %ae %s'
2018-12-06 hinoka [logdog] Increase logs module min instances to 4 (from 2)
2018-12-05 smut [GCE] Detect case where instance already exists
2018-12-05 pprabhu gerrit: Implement SetReview
2018-12-05 vadimsh [lucicfg] Slightly improve error messages by removing redundant info.
2018-12-05 pprabhu gerrit: Expand ChangeInfo returned by GetChange
2018-12-05 pprabhu gerrit: Implement AbandonChange rpc

Created with:
  roll-dep infra/go/src/go.chromium.org/luci

Bug: 900006
Change-Id: I64aba0f88eb3562e077e4edbbd6245d1472a3bc2
Reviewed-on: https://chromium-review.googlesource.com/c/1366219
Auto-Submit: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#19394}
1 file changed
tree: 9ebd342c6ae7e4c21407270bfbde93aa26c6b52f
  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. infra_libs/
  15. node/
  16. packages/
  17. recipes/
  18. test/
  19. utils/
  20. .gitattributes
  21. .gitignore
  22. codereview.settings
  23. CONTRIBUTING.md
  24. DEPS
  25. LICENSE
  26. navbar.md
  27. OWNERS
  28. PRESUBMIT.py
  29. README.md
  30. run.py
  31. test.py
  32. WATCHLISTS
  33. 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.