-
Notifications
You must be signed in to change notification settings - Fork 6
Closed
Description
While looking into #23, I spied the skipped testComm test, and suspected it might be related to some of the issues I've been seeing.
I noticed that there were some ignored errors:
Line 1234 in 6861f4b
| unix.Write(fd, buf) |
Line 1240 in 6861f4b
| unix.Read(fd, buf) |
If I remove the skip and run go test -count=100 -run TestReadRecord/Comm, then every ~100 tests or so I see EBADF returning from those, and sometimes I see hangs while one side or the other is waiting for an eventfd which will never get messaged.
The skip:
Line 548 in 6861f4b
| t.Skip("flaky. TODO(acln): investigate") |
Metadata
Metadata
Assignees
Labels
No labels