mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2025-01-09 19:21:19 +00:00
c1197d7881
* Add static analysis for unsafe uint casting * Fix violations of uintcast * go mod tidy * Add exclusion to nogo for darwin build * Add test for math.Int * Move some things to const so they are assured not to exceed int64 * Self review * lint * fix tests * fix test * Add init check for non 64 bit OS * Move new deps from WORKSPACE to deps.bzl * fix bazel build for go analysis runs * Update BUILD.bazel Remove TODO * add math.AddInt method * Add new test casts * Add case where builtin functions and declared functions are covered * Fix new findings * cleanup Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com> Co-authored-by: Nishant Das <nishdas93@gmail.com> |
||
---|---|---|
.. | ||
comparesame | ||
cryptorand | ||
errcheck | ||
featureconfig | ||
ineffassign | ||
interfacechecker | ||
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/...