go: x/net/http2: TestTransportReturnsUnusedFlowControlMultipleWrites failures

#!watchflakes
post <- pkg == "golang.org/x/net/http2" && test == "TestTransportReturnsUnusedFlowControlMultipleWrites"

Issue created automatically to collect these failures.

Example (log):

panic: test timed out after 20m0s

sync.runtime_Semacquire(0xc000390b60?)
	/workdir/go/src/runtime/sema.go:62 +0x38
sync.(*WaitGroup).Wait(0xc00126e840)
	/workdir/go/src/sync/waitgroup.go:139 +0x94
golang.org/x/net/http2.(*clientTester).run(0xc0009575e0)
	/workdir/gopath/src/golang.org/x/net/http2/transport_test.go:912 +0x1a8
golang.org/x/net/http2.testTransportReturnsUnusedFlowControl(0xc000a07e00?, 0x0)
	/workdir/gopath/src/golang.org/x/net/http2/transport_test.go:3070 +0x120
golang.org/x/net/http2.TestTransportReturnsUnusedFlowControlMultipleWrites(0x2c8950?)
	/workdir/gopath/src/golang.org/x/net/http2/transport_test.go:3080 +0x30
testing.tRunner(0xc000449860, 0x456580)

— watchflakes

About this issue

Original URL
State: closed
Created a year ago
Comments: 154 (9 by maintainers)

Most upvoted comments

unless we’re planning to refresh the x dependencies one more time before the final release. (@golang/release can confirm whether that is the case?)

We create internal vendor branches for x repos at the time of cutting RC 1 (see https://github.com/golang/go/issues/11811#issuecomment-1341141873), and after that point we’ve generally been adding to that branch only the CLs that are necessary to fix release-blocking issues for the given release. So the 1.21 milestone seems okay to start out with here.

dmitshur on Jan 6, 2023