Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls recipe
changes from upstream projects (e.g. depot_tools) into downstream projects
(e.g. tools/build).


More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.
build:
  https://crrev.com/805cc9544d332e89468a045c31434f69a7c6276d CrOS: Update Chromite pin. (dgarrett@google.com)
  https://crrev.com/65505a2ece17e99df41ca6ac2d5a10355fa84e2f Add recipe configs for LARNG+ANSR bot renames. (jbudorick@chromium.org)


TBR=iannucci@chromium.org

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ieb3e7ae48a02b1a41c47e453319e8bd4bce61f26
Reviewed-on: https://chromium-review.googlesource.com/1067096
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
2 files changed
tree: 89214ac1b1383588eb9062951c717a3fc668e4b8
  1. .gitattributes
  2. .gitignore
  3. CONTRIBUTING.md
  4. DEPS
  5. LICENSE
  6. OWNERS
  7. PRESUBMIT.py
  8. README.md
  9. WATCHLISTS
  10. WHITESPACE
  11. appengine/
  12. appengine_module/
  13. bootstrap/
  14. build/
  15. cipd/
  16. codereview.settings
  17. config/
  18. crdx/
  19. data/
  20. doc/
  21. docker/
  22. glyco/
  23. go/
  24. infra/
  25. infra_libs/
  26. navbar.md
  27. node/
  28. packages/
  29. recipes/
  30. roll-deps.py
  31. run.py
  32. test.py
  33. test/
  34. utils/
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.