-=| gregor herrmann, 17.09.2018 00:18:35 +0200 |=- > On Sun, 16 Sep 2018 14:42:05 +0000, Damyan Ivanov wrote: > > > The test passes a thousand runs if the server child ignores SIGPIPE, > > so this looks like the TLSv1.3 shutdown problem when the client makes > > a fast SSL shutdown without waiting for the confirmation from the > > server, then exits, then exits and the server sending its confirmation > > gets SIGPIPEd. > > > https://rt.cpan.org/Ticket/Display.html?id=126899 also talks about > issues around SIGPIPE. > And there's a new 2.060, maybe we should try and check from there.
Oh, nice. Thanks for that notification. I was delving in internals trying to avoid ignoring SIGPIPE. Upstream seems to have gone the other way, ignoring SIGPIPE and documenting the situation. It it suits them, I think it is alright :) I'll run the test suite a hundred times and upload the new upstream release. -- dam
