Google Git
Sign in
chromium / infra / infra / 9c99d4cfd6fadf1d53b5cd9a1a2935d03dc67c6a
commit9c99d4cfd6fadf1d53b5cd9a1a2935d03dc67c6a[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Sat Apr 27 01:00:38 2019
committerCommit Bot <commit-bot@chromium.org>Sat Apr 27 01:00:38 2019
tree022e98d742007f4094483b00ef4b021565fce15f
parent3f7d99bd07276e827e4468978a07da545bccb2df [diff]
Roll infra/go/src/go.chromium.org/luci 5b9784bbf36f..67d0a057ef17 (1 commits)

https://chromium.googlesource.com/infra/luci/luci-go.git/+log/5b9784bbf36f..67d0a057ef17


git log 5b9784bbf36f..67d0a057ef17 --date=short --no-merges --format='%ad %ae %s'
2019-04-27 nodir@google.com [buildbucket] Mention buildbucket hostname


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

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: I9b24bedc8d74e3cd99aa3bb6af1858eb25c2761b
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/1585333
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@{#22627}
1 file changed
tree: 022e98d742007f4094483b00ef4b021565fce15f
  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.