go: x/benchmarks/sweet/cmd/sweet: TestSweetEndToEnd failures

#!watchflakes
post <- pkg == "golang.org/x/benchmarks/sweet/cmd/sweet" && test == "TestSweetEndToEnd"

Issue created automatically to collect these failures.

Example (log):

panic: test timed out after 10m0s
running tests:
	TestSweetEndToEnd (10m0s)

sync.runtime_Semacquire(0xc0004504e8?)
	/workdir/go/src/runtime/sema.go:62 +0x27
sync.(*WaitGroup).Wait(0xc0004504e0)
	/workdir/go/src/sync/waitgroup.go:116 +0xa5
golang.org/x/benchmarks/sweet/cmd/sweet_test.TestSweetEndToEnd(0xc000102ea0)
	/workdir/gopath/src/golang.org/x/benchmarks/sweet/cmd/sweet/integration_test.go:185 +0x1638
testing.tRunner(0xc000102ea0, 0x10e2888)

— watchflakes

About this issue

Original URL
State: open
Created 2 years ago
Comments: 37 (6 by maintainers)

Most upvoted comments

The earlier git failures could be a symptom of port exhaustion (see https://github.com/golang/go/issues/52545#issuecomment-1454157883).

The new clusters of failures are mostly segfaults in the compiler, though. 🤔

bcmills on Nov 15, 2023