https://bugs.winehq.org/show_bug.cgi?id=55203
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zeb Figura z.figura12@gmail.com --- This is very strange; I can't figure out any reasonable reason for this to fail.
The test queues an asynchronous accept with an incorrect size. On Windows this results in the accept being successfully queued. When a connection request comes in the socket will try to fill that async, realize that the size is too small, and instead return failure from the async, with the connection request remaining in the queue for the next accept.
What's odd is that that "next" accept—the one we do just to prove that the connection is still queued—fails to complete synchronously. This doesn't make any sense. There has to be a connection request queued, otherwise the invalid accept wouldn't return. Why would the valid accept fail to complete synchronously?
I thought it might be because the invalid accept doesn't actually wait for a valid connection to come in, but a quick test shows that's not the case.