net: TestPacketConn flaky #5524
Comments
28 June: freebsd/386 building fccd815ed3bb: http://build.golang.org/log/fcded6bcf63bc341dbee9d955c184c977f4c6e7e --- FAIL: TestPacketConn (0.64 seconds) packetconn_test.go:101: PacketConn.WriteTo failed: write unixgram: i/o timeout The read and write deadlines are 100 milliseconds in the test. I'll look at adding some debug logging to this test at some point. |
I'm reopening this. The new OpenBSD builder just hit this error: http://build.golang.org/log/7b3870c037b6135cc3444895259560b2cd599479
And it's 4 CPUs on GCE running a dedicated VM per build revision, so the previous arguments (overloaded, stale processes, too weak) no longer apply. This is just flaky. @mikioh, is this something you could look into? |
I can see it happens on windows-386 builder: http://build.golang.org/log/9e1e98900aa5c5b40fefed8cd0c5e15c5f8d4252 --- FAIL: TestPacketConn (0.38s) Alex |
With a few changes (not pushed to review process yet), we can see some socket and testing goroutine leaks:
Looks like we need to fix mock servers and timeout tests for avoiding some conflicts. |
Interference between test cases are removed by recent changes. Also we don't see this failure at tip, especially after aedee30. Closing. |
The text was updated successfully, but these errors were encountered: