[Weetbix] Show re-clustering progress indicator on cluster page.

Progress indicator will show progress re-clustering algorithms and/or
rules, depending on what is appropriate for the cluster.

TEST=npx cypress run

Change-Id: If2a452ad7681380e0eb4ee56e3289a5f63d0fe7c
Reviewed-on: https://chromium-review.googlesource.com/c/infra/infra/+/3312147
Reviewed-by: Weiwei Lin <weiweilin@google.com>
Reviewed-by: Matthew Warton <mwarton@google.com>
Commit-Queue: Patrick Meiring <meiring@google.com>
Cr-Commit-Position: refs/heads/main@{#45887}
6 files changed
tree: 9104c95ec11fb1ceccb01540adfc5b7c4e602018
  1. .gitallowed
  2. .gitattributes
  3. .gitignore
  4. .style.yapf
  5. .vpython
  6. .vpython3
  7. .yapfignore
  8. 3pp/
  10. DEPS
  12. OWNERS
  13. PRESUBMIT.py
  14. README.md
  17. appengine/
  18. appengine_module/
  19. bootstrap/
  20. build/
  21. chromeperf/
  22. cipd/
  23. codereview.settings
  24. crdx/
  25. doc/
  26. docker/
  27. glyco/
  28. go/
  29. infra/
  30. navbar.md
  31. node/
  32. packages/
  33. python_pb2/
  34. recipes/
  35. run.py
  36. test.py
  37. test/
  38. utils/

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.


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.