Race condition in test_socket.testSockName #95243
Copy link
Copy link
Closed
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtriagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
testSockName has a race condition where find_unused_port() can return a port that gets used by another test in the meantime.
I have a patch, just waiting legal approval.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
testsTests in the Lib/test dirTests in the Lib/test dirtriagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Activity
pythongh-95243: Mitigate the race condition in testSockName
pythongh-95243: Mitigate the race condition in testSockName
gh-95243: Mitigate the race condition in testSockName (#96173)
pythongh-95243: Mitigate the race condition in testSockName (pythonGH…
pythongh-95243: Mitigate the race condition in testSockName (pythonGH…
gh-95243: Mitigate the race condition in testSockName (GH-96173)
gh-95243: Mitigate the race condition in testSockName (GH-96173)
kumaraditya303 commentedon Sep 17, 2022
Fixed by #96173