Google Git
Sign in
chromium / infra / infra / master
commit8d7ee22e2e781baba2ac093ffebc6209229c3a38[log] [tgz]
authorchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>Tue Oct 20 03:42:47 2020
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Oct 20 03:42:47 2020
tree5118addf6e090285e35e15dee019999bb96cfa28
parentb584b5145b416d0215528c83e5ad64bfb641f51a [diff]
Roll luci-go from 6d8956235a95 to e53e0b3ac9f7 (1 revision)

https://chromium.googlesource.com/infra/luci/luci-go.git/+log/6d8956235a95..e53e0b3ac9f7

2020-10-20 yiwzhang@google.com [bbagent] Dynamically compute the wait time for log flushing

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/luci-go-infra-autoroll
Please CC tandrii+infra-roll@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Tbr: tandrii+infra-roll@chromium.org
Change-Id: I7e3de41d4d1d04bcd4b7d667142337eccad9d221
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/2486813
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#35877}
1 file changed
tree: 5118addf6e090285e35e15dee019999bb96cfa28
  1. .gitattributes
  2. .gitignore
  3. .style.yapf
  4. .yapfignore
  5. 3pp/
  6. CONTRIBUTING.md
  7. DEPS
  8. LICENSE
  9. OWNERS
  10. PRESUBMIT.py
  11. README.md
  12. WATCHLISTS
  13. WHITESPACE
  14. appengine/
  15. appengine_module/
  16. bootstrap/
  17. build/
  18. chromeperf/
  19. cipd/
  20. codereview.settings
  21. crdx/
  22. doc/
  23. docker/
  24. glyco/
  25. go/
  26. infra/
  27. navbar.md
  28. node/
  29. packages/
  30. python_pb2/
  31. recipes/
  32. run.py
  33. test.py
  34. test/
  35. 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, run 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. Move 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.

Style

The preferred style is PEP8 with two-space indent; that is, the Chromium Python style, except functions use lowercase_with_underscores. Use yapf (git cl format) to autoformat new code.