prysm-pulse/tools/analyzers
Preston Van Loon 98470fdb13
Update rules_go to v0.29.0 (#10064)
* Update rules_go, delete patch, fix analyzers, remove old deployContract code, and prune old dependency which was broken in rules_go update

* Undo some WORKSPACE diffs

* Gazelle

* remove nofuzz, fix build issue

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2022-01-31 07:06:07 +00:00
..
comparesame Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
cryptorand Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
errcheck Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
featureconfig Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
ineffassign Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
interfacechecker Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
maligned Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
nop Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
properpermissions Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
recursivelock Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
shadowpredecl Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
slicedirect Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
README.md Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00

Running analyzer unit tests

Analyzers' unit tests are ignored in bazel's build files, and therefore are not being triggered as part of the CI pipeline. Because of this they should be invoked manually when writing a new analyzer or making changes to an existing one. Otherwise, any issues will go unnoticed during the CI build.

The easiest way to run all unit tests for all analyzers is go test ./tools/analyzers/...