Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow go-leak linter to fail CI (#5316)
## Which problem is this PR solving? - Part of #5006 - We have only two packages remaining without goroutine leak checks, both integration tests, which are being worked on - Meanwhile new code / packages do not benefit from enforcement of goleak checks because the linter does not fail CI ## Description of the changes - Add the two remaining packages into exclusion list and force a failure of the CI if anything else is missing goleak checks ## How was this change tested? Successful exit: ```shell $ make goleak Verifying that all packages with tests have goleak in their TestMain 🔴 Error(check-goleak): no goleak check in package ./cmd/jaeger/internal/integration/ this package is temporarily allowed and will not cause linter failure 🔴 Error(check-goleak): no goleak check in package ./plugin/storage/integration/ this package is temporarily allowed and will not cause linter failure 🐞 Warning(check-goleak): no goleak check in 2 package(s). See https://github.com/jaegertracing/jaeger/pull/5010/files for examples of adding the checks. ``` Unsuccessful exit (forced by removing one of the existing checks): ```shell $ make goleak Verifying that all packages with tests have goleak in their TestMain 🔴 Error(check-goleak): no goleak check in package ./cmd/jaeger/internal/integration/ this package is temporarily allowed and will not cause linter failure 🔴 Error(check-goleak): no goleak check in package ./internal/tracegen/ 🔴 Error(check-goleak): no goleak check in package ./plugin/storage/integration/ this package is temporarily allowed and will not cause linter failure ⛔ Fatal(check-goleak): no goleak check in 3 package(s), 1 of which not allowed. See https://github.com/jaegertracing/jaeger/pull/5010/files for examples of adding the checks. make: *** [goleak] Error 1 ``` Signed-off-by: Yuri Shkuro <[email protected]>
- Loading branch information