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/eaa41cfed3767db83fd86f88b7df32c7a6799d09 [Chromium recipes] Add shard number to test results milo output (crouleau@chromium.org)
  https://crrev.com/bec06bbd3bbaf09cbf33176512a4b1d8a1a60307 chromium_tests: fix android_cronet_tester configuration. (jbudorick@chromium.org)
  https://crrev.com/d976667f5371af8090f3b25e7a2f3fc40c78328a chromium_tests: Recipe configuration for win-pixel-browser-tests-rel. (svenzheng@chromium.org)
  https://crrev.com/e2d9129d0f321097e96d828dae7a979f461c9a34 [flutter-engine] Fix the list of uploaded MacOS artifacts (jsimmons@google.com)
  https://crrev.com/4bda7fc4d6183af0855aaf39f1b1a1351f8e0f6a chromium_swarming: Return has_valid_results (martiniss@chromium.org)
depot_tools:
  https://crrev.com/a541b28d4eba269fa7a4d3427ba9e04057053415 Add 'X in tuple()' support to gclient conditionals. (bpastene@chromium.org)
  https://crrev.com/54434e7e1dabdc79232c3eeca06c44e5c0aabab9 Ignore git submodules when calculating dirty files. (eliribble@chromium.org)
recipe_engine:
  https://crrev.com/812fc275e67c06d6fd5c3f9ee52ed145555e3bd0 Add gevent to recipe engine. (iannucci@chromium.org)
  https://crrev.com/318a18a4f0481d5eac3ed195b241867dc2749298 Fix accidental regression due to rebase flub. (iannucci@chromium.org)
  https://crrev.com/96bcf6aaa92a254a19c1120b446dd6b35e8dc902 Revert gevent from recipe engine for now. (iannucci@chromium.org)
  https://crrev.com/f4b41ab0783dba26b58eb476fe13c3feb20c7e79 Move Step and Command to non-internal file for post-process inputs. (gbeaty@chromium.org)


TBR=iannucci@chromium.org

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