Thanks to visit codestin.com
Credit goes to github.com

Skip to content

EBADF in testComm #24

@pwaller

Description

@pwaller

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:

unix.Write(fd, buf)

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:

t.Skip("flaky. TODO(acln): investigate")

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions