Add sanitized_anchor_name to go deps

This is a dependency of blackfriday

Output from deps.py update:

Updated repos:
https://code.googlesource.com/gocloud.git/+log/a5c6324a6e84..a93970efcf20
https://chromium.googlesource.com/external/github.com/aws/aws-sdk-go.git/+log/8234000fff96..29ae2fc88231
https://chromium.googlesource.com/external/github.com/kisielk/errcheck.git/+log/9e642955b59d..e14f8d59a22d
https://chromium.googlesource.com/external/github.com/matttproud/golang_protobuf_extensions.git/+log/c12348ce28de..c182affec369
https://chromium.googlesource.com/external/github.com/pkg/errors.git/+log/059132a15dd0..ba968bfe8b2f
https://chromium.googlesource.com/external/github.com/prometheus/client_golang.git/+log/3ba18b203370..fb3d5cb2ad57
https://chromium.googlesource.com/external/github.com/prometheus/procfs.git/+log/1dc9a6cbc91a..14fa7590c24d
https://chromium.googlesource.com/external/github.com/stretchr/testify.git/+log/c45a1382af90..ffdc059bfe9c
https://skia.googlesource.com/buildbot.git/+log/3e15e766dae7..ae4a64ed878f
https://chromium.googlesource.com/external/github.com/google/starlark-go.git/+log/2c1f36271ed6..746fad3713e3
https://go.googlesource.com/crypto.git/+log/505ab145d0a9..ff983b9c42bc
https://go.googlesource.com/tools.git/+log/d00ac6d27372..8a6051197512
https://code.googlesource.com/google-api-go-client.git/+log/65a46cafb132..19e022d8cf43
https://chromium.googlesource.com/external/github.com/grpc/grpc-go.git/+log/36f3126920fe..c71aa62423b3

Bug: 850113
Change-Id: I2f03e100aeee2f2533967f27b6996e8dd9e91078
Reviewed-on: https://chromium-review.googlesource.com/c/1394211
Reviewed-by: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#19765}
2 files changed
tree: 433078aae6c031fcda9e0ac1cb03f12f3187f7d0
  1. .gitattributes
  2. .gitignore
  3. 3pp/
  4. CONTRIBUTING.md
  5. DEPS
  6. LICENSE
  7. OWNERS
  8. PRESUBMIT.py
  9. README.md
  10. WATCHLISTS
  11. WHITESPACE
  12. appengine/
  13. appengine_module/
  14. bootstrap/
  15. build/
  16. cipd/
  17. codereview.settings
  18. crdx/
  19. data/
  20. doc/
  21. docker/
  22. glyco/
  23. go/
  24. infra/
  25. navbar.md
  26. node/
  27. packages/
  28. recipes/
  29. run.py
  30. test.py
  31. test/
  32. 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.
  • 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.