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/ca3b222609ec3bdd41bcb1473441acea15eeb31e Use a cache directory for pdfium bots. (thakis@chromium.org)
  https://crrev.com/1245fd5c22518f9897019559e3344464e3f7d1ee Update post-process checks to use StatusAnyFailure or StatusException (sergiyb@chromium.org)
  https://crrev.com/00887af6b00e0ed804c907fec91c28dd47002dc4 Pick up depot_tools revert. (iannucci@chromium.org)
depot_tools:
  https://crrev.com/245337d62e22e410b8c3f7a037e9c34252a72aef Pass target branch from tryserver in bot_update module (whesse@google.com)
  https://crrev.com/151c3484da58fa02f7d2c69454be3cb4e3395d05 Replace post-process checks with ones that are not deprecated (sergiyb@chromium.org)
  https://crrev.com/4809957b795006ffa9fd1b43e402a3b9e2cb7fe4 [cpplint] Ignore fn_size check for macros with digits (qyearsley@chromium.org)
  https://crrev.com/91a32c5e39d2c1e789e7fe63355bc2ec399f68db CppLint changes for VSCode cpplint plugin (jophba@chromium.org)
  https://crrev.com/298f2cf820dfe45dff53b0e41b11441dbf72b48c git cl: Print a clear error message when we fail to find the remote url. (ehmaldonado@chromium.org)
  https://crrev.com/d7f7a3eb92a43b9135bfb8672c9af0fa1c9bce9a [lucicfg] Bump lucicfg version 1.2.0 -> 1.3.2. (vadimsh@chromium.org)
  https://crrev.com/5585c87a78b77d4bdab2a58f636ced7918b6b021 Revert "Pass target branch from tryserver in bot_update module" (tandrii@chromium.org)
recipe_engine:
  https://crrev.com/6605f1b0db4ddee8e7f40b73fe60cf5f8cbe794f Make StatusFailure work for non-exceptional failures only (sergiyb@chromium.org)
  https://crrev.com/16dfe87b81be9acfd9e1763b20bd028f81d28e13 cq: add API to track triggered_build_ids. (tandrii@chromium.org)


TBR=iannucci@chromium.org

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I7352c5c574558bc66ea453b5254f63e8229c26b0
Reviewed-on: https://chromium-review.googlesource.com/c/1484553
Reviewed-by: Recipe Roller <recipe-roller@chromium.org>
Commit-Queue: Recipe Roller <recipe-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#20878}
2 files changed
tree: acdb1d0f3cc03abaa6c0a603b252acef2630ba7e
  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.