mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-22 03:30:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
38f208d70d
prysm-pulse/tools/analyzers
History
terence 5a66807989
Update to V5 (#13622) 
* First take at updating everything to v5

* Patch gRPC gateway to use prysm v5

Fix patch

* Update go ssz

---------

Co-authored-by: Preston Van Loon <pvanloon@offchainlabs.com>
2024-02-15 05:46:47 +00:00
..
comparesame Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
cryptorand Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
errcheck Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
featureconfig Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
gocognit Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
ineffassign Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
interfacechecker Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
logruswitherror Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
maligned Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
nop Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
properpermissions Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
recursivelock Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
shadowpredecl Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
slicedirect Update to V5 (#13622) 2024-02-15 05:46:47 +00:00
uintcast Update to V5 (#13622) 2024-02-15 05:46:47 +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/...