On Mon, Sep 27, 2021 at 11:53:07AM +0530, Amit Kapila wrote: > So, it seems on your machine it has passed the following condition in > secure_write: > if (n < 0 && !port->noblock && (errno == EWOULDBLOCK || errno == EAGAIN))
Yep. > If so, this indicates write failure which seems odd to me and probably > something machine-specific or maybe some different settings in your > build or machine. BTW, if SSL or GSS is enabled that might have caused > it in some way. I think the best way is to debug the secure_write > during this occurrence. Yeah, but we don't use any of them in the context of this test, so this is something on a simple send(), no? Hmm. That would not be the first issue we see with macos these days with interrupted syscalls... And actually in this stack I can see that errno gets set to EINTR. -- Michael
signature.asc
Description: PGP signature
