Google Git
Sign in
chromium / infra / infra / 70890ac4ebd49accb4d9708c36c53483ea8d939d
commit70890ac4ebd49accb4d9708c36c53483ea8d939d[log] [tgz]
authorrecipe-roller <recipe-roller@chromium.org>Thu Feb 07 22:46:24 2019
committerCommit Bot <commit-bot@chromium.org>Thu Feb 07 22:46:24 2019
tree89bd2b3646aeaa61d1202cd6cd633517e40223e1
parentf95930c9245ee2f04331a3ca8473291c3ef41689 [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.
build:
  https://crrev.com/0cb72e58cbb826c50eeeff9d31ac4c9dda2a3311 use goma.chromium.org (ukai@google.com)
  https://crrev.com/783f139826463ef69d175bb3c6571c485487c1e5 Stop downloading webrtc_test_resources on testers, it's only needed on builders (oprypin@webrtc.org)
  https://crrev.com/d854dc2cd7ea8f5e683eaf5bc9811ad9d9b8e1ad WebRTC: Split webrtc.run_mb() call out of webrtc.compile() (oprypin@webrtc.org)
  https://crrev.com/5863e0060297faba7f9068be26e0d508a584a922 WebRTC: Rework iOS recipe to not use src-side config (oprypin@webrtc.org)
  https://crrev.com/488838903e4e77304095459000cd307cf57f0584 fix gradlew, coveralls (dnfield@google.com)
  https://crrev.com/23056466c4279f80d82709db9fe8b7067fac6c83 Use full step name for FindIt Flakiness metadata. (erikchen@chromium.org)
  https://crrev.com/ff4beb920ed37c3d6f7b78d1d44896e952c8137f Fix chromebots (dnfield@google.com)
  https://crrev.com/037a5eeab854bafde465e39c0712a80d6ff0d24b Add high bitrate tests to the webrtc recipe (emircan@chromium.org)
  https://crrev.com/0aac1ab52e7b3e15ae3e795886579b90a9840a8b Remove the hacky way for WebRTC to hook into chromium_tests (oprypin@webrtc.org)
depot_tools:
  https://crrev.com/484d74fa21a52aeee2665671d970b999291d5900 Add 'chromeos' as one of the DEPS_OS_CHOICES. (mmoss@google.com)
  https://crrev.com/a2d5f784774876381847d753ee3cf98dc778363b Add fetch config for new node-ci repository. (machenbach@chromium.org)
recipe_engine:
  https://crrev.com/acaaf39516da65c2cad56e8e10c4731c3fc539df [swarming] Fix analyze() bug (joshuaseaton@google.com)
  https://crrev.com/cc676548eec015636830abd3a8c53c40cd8460a6 [swarming] Add support for outputs (joshuaseaton@google.com)


TBR=iannucci@chromium.org

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