Google Git
Sign in
chromium / experimental / codesearch / infra / infra / df2db378a9a388bfe7e0aac1b86c3eaf7b578e2f
commitdf2db378a9a388bfe7e0aac1b86c3eaf7b578e2f[log] [tgz]
authorJulie Hockett <juliehockett@google.com>Tue Jan 15 23:58:28 2019
committerCommit Bot <commit-bot@chromium.org>Tue Jan 15 23:58:28 2019
treeba6e3a8f47a1c7300c9707987ea31ff2722e8ad8
parent81d96b292229d1f3dedc1ecc716b06298a656627 [diff]
[tricium] Pass along deadline to recipe run

The deadline is now propagated to the buildbucket call through
execution_timeout_secs.

Change-Id: Ib4f30146d551c586535ade292c2456392991266d
Reviewed-on: https://chromium-review.googlesource.com/c/1412051
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Julie Hockett <juliehockett@google.com>
Cr-Commit-Position: refs/heads/master@{#20005}
Cr-Mirrored-Commit: 1a7c79bc6ce834ddb112e4a04674f31878bbb1a0
2 files changed
tree: ba6e3a8f47a1c7300c9707987ea31ff2722e8ad8
  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. luci
  20. recipes-py
  21. .gitattributes
  22. .gitignore
  23. .gitmodules
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. navbar.md
  29. OWNERS
  30. PRESUBMIT.py
  31. README.md
  32. run.py
  33. test.py
  34. WATCHLISTS
  35. 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.
  • 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.