Google Git
Sign in
chromium / infra / infra / b489690463986d6921857a28cd7de5e131ff10a3
commitb489690463986d6921857a28cd7de5e131ff10a3[log] [tgz]
authorMarc-Antoine Ruel <maruel@chromium.org>Thu Feb 07 20:12:18 2019
committerCommit Bot <commit-bot@chromium.org>Thu Feb 07 20:12:18 2019
tree988a081a9e66a63421bff4ebeed391b8f9931772
parent21376f17e0e6a43e6417a88a33d2109b1e1ddd04 [diff]
Roll infra/go/src/go.chromium.org/luci/ e48c958d0..44257920e (6 commits)

Include relevant compile fixes.

tricium will require more follow up fixes.

https://chromium.googlesource.com/infra/luci/luci-go/+log/e48c958d0748..44257920eddf

$ git log e48c958d0..44257920e --date=short --no-merges --format='%ad %ae %s'
2019-02-06 maruel isolated: Make it support other algorithms
2019-02-06 tikuta [swarming] clean up directory before downloading content
2019-02-06 maruel [isolated] Add partial support for SHA256 and SHA512
2019-02-05 seanabraham lucicfg: Update reference_design documentation.
2019-02-05 seanabraham lucicfg: Add proto to represent Chrome OS CQ test plan requirements.
2019-02-05 maruel Make isolatedfake support multiple namespaces

Created with:
  roll-dep infra/go/src/go.chromium.org/luci

Change-Id: Icdd1ccfbe061b1b9c8ba9a19a1f30bb60bea0cdd
Reviewed-on: https://chromium-review.googlesource.com/c/1457205
Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Commit-Queue: Marc-Antoine Ruel <maruel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#20523}
4 files changed
tree: 988a081a9e66a63421bff4ebeed391b8f9931772
  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.