mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-20 16:41:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
prysm-pulse/tools/analyzers
History
Preston Van Loon 4b033f4cc7
Update go to 1.19.3 (#11630) 
* Update go to 1.19.3

* Update other items to 1.19

* Update golangci-lint to latest release

* Run gofmt -s with go1.19

* Huge gofmt changes

Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
2022-11-18 19:12:19 +00:00
..
comparesame
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
cryptorand
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
errcheck
Update go to 1.19.3 (#11630)
2022-11-18 19:12:19 +00:00
featureconfig
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
gocognit
Update go to 1.19.3 (#11630)
2022-11-18 19:12:19 +00:00
ineffassign
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
interfacechecker
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
logruswitherror
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
maligned
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
nop
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
properpermissions
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
recursivelock
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
shadowpredecl
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
slicedirect
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
uintcast
Add V3 Suffix to All Prysm Packages (#11083)
2022-08-16 12:20:13 +00:00
README.md
Fix failing static analyzer tests (#7363)
2020-09-29 11:29:40 +00:00

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/...