mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-03 08:37:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
49c73e65a1
prysm-pulse/tools/analyzers
History
Chase Jeter 0ea4b02b8b
Added analyzer for detecting recursive/nested mutex read locks. (#10066) 
* Added analyzer for detecting recursive/nested mutex read locks.

* Added type assertion checks and removed unused 'iTypes' directory

* Clean up

* Bazel file fixes

* Cleaned up code and added comments.

Co-authored-by: Raul Jordan <raul@prysmaticlabs.com>
2022-01-14 17:12:21 +08:00
..
comparesame Fix comments (#8802) 2021-04-23 12:06:05 +00:00
cryptorand Add pkg crypto (#9603) 2021-09-15 22:55:11 +00:00
errcheck Move Shared/Testutil into Testing (#9659) 2021-09-23 18:53:46 +00:00
featureconfig Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
ineffassign Various code cleanups (#8889) 2021-05-13 08:29:14 +02:00
interfacechecker Add Metadata V2 Object and Interface (#8962) 2021-06-02 13:44:34 +08:00
maligned Fix comments (#8802) 2021-04-23 12:06:05 +00:00
nop Fix comments (#8802) 2021-04-23 12:06:05 +00:00
properpermissions Move Shared Packages into Math/ and IO/ (#9622) 2021-09-17 21:55:24 +00:00
recursivelock Added analyzer for detecting recursive/nested mutex read locks. (#10066) 2022-01-14 17:12:21 +08:00
shadowpredecl Fix comments (#8802) 2021-04-23 12:06:05 +00:00
slicedirect Fix comments (#8802) 2021-04-23 12:06:05 +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/...