Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Here's what I see wrt to socket.t when running the test suite:
io/socket.t ........................................................ 1/?
However, the test summary regards that as a FAIL:
Running that test script outside of Test::Harness appears to be ok:
This is the same on both 32-bit and 64-bit builds.
On Sun, Oct 21, 2018 at 02:17:28AM -0700, sisyphus (via RT) wrote:
No, that's a fail, there's no plan (1..21) because both threads die
Yeah, I'm not sure what the underlying problem is.
The binmode() before the die in each "process" isn't removing the
Tomorrow I'll add a skip for that block (it's 10pm) and go back to
On Sun, 21 Oct 2018 13:16:56 +0200, Tony Cook <email@example.com> wrote:
Note for context: This was caused specifically by 9704d77 immediately upon introduction and was caught by my Win32 smoker on test-smoke.org
On Sun, Oct 21, 2018 at 08:40:11PM +0200, Christian Walde wrote:
The cause of that test failing is fixed by dda4a47.
Thank you for filing this report. You have helped make Perl better.
With the release today of Perl 5.30.0, this and 160 other issues have been
Perl 5.30.0 may be downloaded via:
If you find that the problem persists, feel free to reopen this ticket.