prysm-pulse/tools/analyzers
Preston Van Loon 7cc32c4dda
Various code inspection resolutions (#7438)
* remove unused code

* remove defer use in loop

* Remove unused methods and constants

* gofmt and gaz

* nilness check

* remove unused args

* Add TODO for refactoring subscribeWithBase to remove unused arg. It seems too involved to include in this sweeping PR. https://github.com/prysmaticlabs/prysm/issues/7437

* replace empty slice declaration

* Remove unnecessary type conversions

* remove redundant type declaration

* rename receivers to be consistent

* Remove bootnode query tool. It is now obsolete by discv5

* Remove relay node. It is no longer used or supported

* Revert "Remove relay node. It is no longer used or supported"

This reverts commit 4bd7717334dad85ef4766ed9bc4da711fb5fa810.

* Delete unused test directory

* Delete unsupported gcp startup script

* Delete old k8s script

* build fixes

* fix build

* go mod tidy

* revert slasher/db/kv/block_header.go

* fix build

* remove redundant nil check

* combine func args

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
Co-authored-by: Victor Farazdagi <simple.square@gmail.com>
2020-10-12 08:11:05 +00:00
..
comparesame Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
cryptorand Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
errcheck Apply testutils assertions: final cleanup (#7003) 2020-08-25 15:23:06 +00:00
featureconfig Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
ineffassign Fix deepsource findings (#7457) 2020-10-08 08:36:47 +00:00
maligned Various code inspection resolutions (#7438) 2020-10-12 08:11:05 +00:00
nop Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
shadowpredecl Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
slicedirect Unnecessary Slice-to-Slice Conversion analyzer (#7321) 2020-09-23 16:14:34 +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/...