perl 5.26.0 build reports failed tests using perlbrew

[robertoabraham]

This bug-tracker is monitored by developers and other technical types. We like detail! So please use this form and tell us, concisely but precisely, what's up. Please fill out ALL THE FIELDS!

If you have a feature request, please post to the UserVoice. If you're reporting a BSOD, don't post here! Instead, e-mail "[email protected]", and if possible attach the minidump from "C:\Windows\minidump".

• Your Windows build number: (Type ver at a Windows Command Prompt)

Version 10.0.16215.1000

• What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)

perlbrew install perl-5.26.0

• What's wrong / what should be happening instead:

The build fails reporting the following summary of test failures in the error log:

Test Summary Report

io/sem.t (Wstat: 5632 Tests: 1 Failed: 0)
Non-zero exit status: 22
Parse errors: Bad plan. You planned 7 tests but ran 1.
io/shm.t (Wstat: 0 Tests: 15 Failed: 14)
Failed tests: 2-15
io/socket.t (Wstat: 0 Tests: 15 Failed: 1)
Failed test: 11
../cpan/IO-Socket-IP/t/31nonblocking-connect-internet.t (Wstat: 29440 Tests: 8 Failed: 1)
Failed test: 3
Non-zero exit status: 115
Parse errors: No plan found in TAP output
../cpan/IPC-SysV/t/ipcsysv.t (Wstat: 5632 Tests: 7 Failed: 0)
Non-zero exit status: 22
Parse errors: Bad plan. You planned 39 tests but ran 7.
../cpan/IPC-SysV/t/sem.t (Wstat: 5632 Tests: 1 Failed: 0)
Non-zero exit status: 22
Parse errors: Bad plan. You planned 11 tests but ran 1.
../cpan/IPC-SysV/t/shm.t (Wstat: 3328 Tests: 2 Failed: 1)
Failed test: 2
Non-zero exit status: 13
Parse errors: Bad plan. You planned 23 tests but ran 2.
../dist/Net-Ping/t/510_ping_udp.t (Wstat: 256 Tests: 2 Failed: 1)
Failed test: 2
Non-zero exit status: 1
Files=2553, Tests=1230362, 2196 wallclock secs (107.41 usr 122.59 sys + 609.17 cusr 494.53 csys = 1333.70 CPU)
Result: FAIL
makefile:832: recipe for target 'test_harness' failed
make: *** [test_harness] Error 18

Brew Failed

• Strace of the failing command, if applicable: (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

See our contributing instructions for assistance.

[stehufntdev]

Thanks for reporting the issue. Looking at the names of the tests above, it is likely known missing functionality in WSL. Outside of the test failures, is this blocking development with perl?

[robertoabraham]

Hi, aside from the test failures, things have been fine for me so far. I forced the install without the tests and so far I haven't run up against any problems.

[stehufntdev]

Thanks for confirming! As I mentioned these are likely all known issues but I'll mark it as a bug so we can track getting the tests to run clean.

[therealkenc]

Just from the test summary output (absent an strace) you've got #1967. #1584, #1016. More the merrier.

[ghost]

Ok so perl itself works; it's only the tests that fail I guess? May be annoying but is probably not of highest priority I suppose.

[sudhirj]

@robertoabraham How did you force install without tests?

[robertoabraham]

@sudhirj I just used the --notest switch on the install command. It's described in the perlbrew manpage.

Sorry for the slow reply - I'm traveling at the moment.

[sudhirj]

Thanks... Perl was holding out Postgres for me, but with this out of the way I can actually give WSL a shot for work.

[JJ]

I seem to be having another issue:

# Failed test 21 - [perl \#128020] long body lines are wrapped: maxlen 1278 at ../lib/perlbug.t line 154

This is a:

Operating system name? [linux]  
 
Operating system version? [3.13.0-34-generic]  
You are using GNU cc 4.8.4.

Any hint on what's missing or needs upgrade? It's an Ubuntu server 14.04LTS otherwise

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!