Google Git
Sign in
chromium / codesearch / infra / infra / 9d64e9059b2354f19c3531bfc500798a3a63a307
commit9d64e9059b2354f19c3531bfc500798a3a63a307[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Fri May 17 03:44:16 2019
committerCommit Bot <commit-bot@chromium.org>Fri May 17 03:44:16 2019
tree42330b92a155c1e9ba9a8decc333e6d5ab456dd5
parent56d8de76ee0538e8a39163c36e0ea118d20fc120 [diff]
Roll infra/go/src/go.chromium.org/luci 3f45e00083f6..7ccb2d28fc99 (1 commits)

https://chromium.googlesource.com/infra/luci/luci-go.git/+log/3f45e00083f6..7ccb2d28fc99


git log 3f45e00083f6..7ccb2d28fc99 --date=short --no-merges --format='%ad %ae %s'
2019-05-17 vadimsh@chromium.org [server] Add helpers for running background goroutines.


Created with:
  gclient setdep -r infra/go/src/go.chromium.org/luci@7ccb2d28fc99

The AutoRoll server is located here: https://autoroll.skia.org/r/luci-go-infra-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=tandrii+infra-roll@chromium.org

Change-Id: I4d00c756d4c21fbbb13fa3330d51b867a68340ba
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1617061
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#23028}
1 file changed
tree: 42330b92a155c1e9ba9a8decc333e6d5ab456dd5
  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. .gitattributes
  20. .gitignore
  21. codereview.settings
  22. CONTRIBUTING.md
  23. DEPS
  24. LICENSE
  25. navbar.md
  26. OWNERS
  27. PRESUBMIT.py
  28. README.md
  29. run.py
  30. test.py
  31. WATCHLISTS
  32. 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, 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.