You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
prometheus/vendor/go.uber.org/goleak
Julien Pivotto d668a7efe3
Update go dependencies (#7837)
4 years ago
..
internal/stack tsdb: test for leaks (#7566) 4 years ago
.gitignore tsdb: test for leaks (#7566) 4 years ago
.travis.yml Update go dependencies (#7837) 4 years ago
CHANGELOG.md Update go dependencies (#7837) 4 years ago
LICENSE tsdb: test for leaks (#7566) 4 years ago
Makefile tsdb: test for leaks (#7566) 4 years ago
README.md Update go dependencies (#7837) 4 years ago
doc.go tsdb: test for leaks (#7566) 4 years ago
glide.yaml tsdb: test for leaks (#7566) 4 years ago
go.mod tsdb: test for leaks (#7566) 4 years ago
go.sum tsdb: test for leaks (#7566) 4 years ago
leaks.go tsdb: test for leaks (#7566) 4 years ago
options.go Update go dependencies (#7837) 4 years ago
testmain.go tsdb: test for leaks (#7566) 4 years ago
tools.go tsdb: test for leaks (#7566) 4 years ago

README.md

goleak GoDoc Build Status Coverage Status

Goroutine leak detector to help avoid Goroutine leaks.

Installation

You can use go get to get the latest version:

go get -u go.uber.org/goleak

goleak also supports semver releases. It is compatible with Go 1.5+.

Quick Start

To verify that there are no unexpected goroutines running at the end of a test:

func TestA(t *testing.T) {
	defer goleak.VerifyNone(t)

	// test logic here.
}

Instead of checking for leaks at the end of every test, goleak can also be run at the end of every test package by creating a TestMain function for your package:

func TestMain(m *testing.M) {
	goleak.VerifyTestMain(m)
}

Determine Source of Package Leaks

When verifying leaks using TestMain, the leak test is only run once after all tests have been run. This is typically enough to ensure there's no goroutines leaked from tests, but when there are leaks, it's hard to determine which test is causing them.

You can use the following bash script to determine the source of the failing test:

# Create a test binary which will be used to run each test individually
$ go test -c -o tests

# Run each test individually, printing "." for successful tests, or the test name
# for failing tests.
$ for test in $(go test -list . | grep -E "^(Test|Example)"); do ./tests -test.run "^$test\$" &>/dev/null && echo -n "." || echo "\n$test failed"; done

This will only print names of failing tests which can be investigated individually. E.g.,

.....
TestLeakyTest failed
.......

Stability

goleak is v1 and follows SemVer strictly.

No breaking changes will be made to exported APIs before 2.0.