mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2024-12-23 03:51:29 +00:00
4c916403e9
* Enable dupword linter & fix findings * Correct an incorrect fix * Add nolint comment * Add another nolint comment * Revert unintended change to bazel version --------- Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com> Co-authored-by: Radosław Kapka <rkapka@wp.pl> |
||
|---|---|---|
| .. | ||
| comparesame | ||
| cryptorand | ||
| errcheck | ||
| featureconfig | ||
| gocognit | ||
| ineffassign | ||
| interfacechecker | ||
| logruswitherror | ||
| maligned | ||
| nop | ||
| properpermissions | ||
| recursivelock | ||
| shadowpredecl | ||
| slicedirect | ||
| uintcast | ||
| README.md | ||
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/...