Google Git
Sign in
chromium / experimental / codesearch / infra / infra / d844f131baab613d13826cb23b2ef8bb0f58a392
commitd844f131baab613d13826cb23b2ef8bb0f58a392[log] [tgz]
authorrecipe-roller <recipe-roller@chromium.org>Tue Jan 15 22:56:42 2019
committerCommit Bot <commit-bot@chromium.org>Tue Jan 15 22:56:42 2019
treeb43de2670838c66b47d61885dc8712704e3c300e
parent221f23b3542b33a8eff941aeeaa9d775fe07f07f [diff]
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.
recipe_engine:
  https://crrev.com/2f65b24e319f41a6009c857b1928cb2f7aea9c45 Remove env, unused third party dependencies. (iannucci@chromium.org)


TBR=iannucci@chromium.org

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I193e6fd1bbd2fe0c9d70c38a1499685541f4c448
Reviewed-on: https://chromium-review.googlesource.com/c/1412645
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#20002}
Cr-Mirrored-Commit: edba19d90c78a1705f18350c1f90d746c50391fc
2 files changed
tree: b43de2670838c66b47d61885dc8712704e3c300e
  1. .gitattributes
  2. .gitignore
  3. .gitmodules
  4. 3pp/
  5. CONTRIBUTING.md
  6. DEPS
  7. LICENSE
  8. OWNERS
  9. PRESUBMIT.py
  10. README.md
  11. WATCHLISTS
  12. WHITESPACE
  13. appengine/
  14. appengine_module/
  15. bootstrap/
  16. build/
  17. cipd/
  18. codereview.settings
  19. crdx/
  20. data/
  21. doc/
  22. docker/
  23. glyco/
  24. go/
  25. infra/
  26. luci
  27. navbar.md
  28. node/
  29. packages/
  30. recipes-py
  31. recipes/
  32. run.py
  33. test.py
  34. test/
  35. 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.