mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 04:47:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
155d60dd60
prysm-pulse/tools/analyzers
History
Preston Van Loon d17826fb9d
Static Analyzer: require log.WithError instead of log.Errorf("bad: %v", err) (#11143) 
* Add analysis template with failing test

* Works for the most common use case

* Progress on tool and more test cases

* Improvements

* handle nil

* works for the most part

* Fix some TODOs in the tool

* Fix some TODOs in the tool
2022-08-01 16:08:01 +00:00
..
comparesame Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
cryptorand Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
errcheck Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
featureconfig Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
gocognit Massive code cleanup (#10913) 2022-06-27 13:34:38 +00:00
ineffassign Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
interfacechecker Update rules_go to v0.29.0 (#10064) 2022-01-31 07:06:07 +00:00
logruswitherror Static Analyzer: require log.WithError instead of log.Errorf("bad: %v", err) (#11143) 2022-08-01 16:08:01 +00:00
maligned Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
nop Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
properpermissions Replace ioutil with io and os (#10541) 2022-04-18 20:42:07 +00:00
recursivelock Massive code cleanup (#10913) 2022-06-27 13:34:38 +00:00
shadowpredecl Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
slicedirect Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +00:00
uintcast Add static analysis for unsafe uint casting (#10318) 2022-03-11 09:34:30 +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/...