mirror of https://github.com/OffchainLabs/prysm.git synced 2026-05-02 03:02:54 -04:00

Files

terencechain d17996f8b0 Update to V4 🚀 (#12134 )

* Update V3 from V4

* Fix build v3 -> v4

* Update ssz

* Update beacon_chain.pb.go

* Fix formatter import

* Update update-mockgen.sh comment to v4

* Fix conflicts. Pass build and tests

* Fix test

2023-03-17 18:52:56 +00:00

comparesame

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

cryptorand

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

errcheck

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

featureconfig

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

gocognit

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

ineffassign

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

interfacechecker

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

logruswitherror

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

maligned

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

nop

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

properpermissions

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

recursivelock

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

shadowpredecl

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

slicedirect

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +00:00

uintcast

Update to V4 🚀 (#12134 )

2023-03-17 18:52:56 +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/...