lockedfile: pull in workaround for spurious EDEADLK on platforms using fcntl #91
Comments
myitcv
added a commit
that referenced
this issue
Mar 13, 2020
Apply upstream CL 222277 per @bcmills Automatically applied via: (command cd /path/to/go; git diff c6f678b6efd6622d335e6d4b659282bb2d16f5ba~1 c6f678b6efd6622d335e6d4b659282bb2d16f5ba) | git apply -p5 with a minor fix to then use github.com/rogpeppe/go-internal/testenv instead of internal/testenv Fixes #91
rogpeppe
pushed a commit
that referenced
this issue
May 6, 2020
) Apply upstream CL 222277 per @bcmills Automatically applied via: (command cd /path/to/go; git diff c6f678b6efd6622d335e6d4b659282bb2d16f5ba~1 c6f678b6efd6622d335e6d4b659282bb2d16f5ba) | git apply -p5 with a minor fix to then use github.com/rogpeppe/go-internal/testenv instead of internal/testenv Fixes #91
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CL 222277 adds a workaround for the long-standing¹ bug that deadlock detection in most (all?)
fcntlimplementations operates on processes rather than threads.For portability, it's probably worth patching in.
¹https://bugzilla.mozilla.org/show_bug.cgi?id=62457#c5
The text was updated successfully, but these errors were encountered: