TestGetFailures sometimes fails

[aschmahmann]

TestGetFailures sometimes fails. When running tests with -race it's very easy to trigger the failure.

go-libp2p-kad-dht/ext_test.go

Line 21 in ef31967

func TestGetFailures(t *testing.T) {

=== RUN   TestGetFailures
panic: io: read/write on closed pipe

goroutine 274 [running]:
github.com/libp2p/go-libp2p-kad-dht.TestGetFailures.func2(0x102e820, 0xc000004460)
        C:/Users/adin/go/src/github.com/libp2p/go-libp2p-kad-dht/ext_test.go:72 +0x
48f
github.com/libp2p/go-libp2p/p2p/host/basic.(*BasicHost).SetStreamHandler.func1(0xc0
00018150, 0xf, 0x5900030, 0xc000004460, 0xf, 0xc000054220)
        C:/Users/adin/go/pkg/mod/github.com/libp2p/go-libp2p@v0.4.2/p2p/host/basic/
basic_host.go:393 +0xbc
created by github.com/libp2p/go-libp2p/p2p/host/basic.(*BasicHost).newStreamHandler

        C:/Users/adin/go/pkg/mod/github.com/libp2p/go-libp2p@v0.4.2/p2p/host/basic/
basic_host.go:291 +0x873
exit status 2

The tests fails occur at

go-libp2p-kad-dht/ext_test.go

Lines 71 to 72 in ef31967

	if err := pbr.ReadMsg(pmes); err != nil {
	panic(err)

[Stebalien]

Discussed in person. Conclusion: ignore the error.