Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 598338

Summary: dev-lang/perl-5.22.2 fails tests op/fork.t, cpan/Socket/t/Socket.t, dist/Net-Ping/t/510_ping_udp.t on hardened
Product: Gentoo Linux Reporter: ephemer0l <om>
Component: Current packagesAssignee: The Gentoo Linux Hardened Team <hardened>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kentnl, kingjon3377, perl
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build.log
emerge --info =dev-lang/perl-5.22.2

Description ephemer0l 2016-10-28 10:57:55 UTC
Created attachment 451740 [details]
build.log

Builld log attached.
Comment 1 ephemer0l 2016-10-28 10:58:48 UTC
Created attachment 451742 [details]
emerge --info =dev-lang/perl-5.22.2
Comment 2 Kent Fredric (IRC: kent\n) (RETIRED) gentoo-dev 2016-10-28 11:07:35 UTC
/bin/bash: /var/tmp/portage/dev-lang/perl-5.22.2/work/perl-5.22.2/perl: Resource temporarily unavailable
/bin/bash: /var/tmp/portage/dev-lang/perl-5.22.2/work/perl-5.22.2/perl: Success
# Failed test 28 - bash/zsh-only test for 'fork' returning undef on failure at op/fork.t line 39
#      got ""
# expected "ok"

^ Weird, but I've seen this *sort* of problem before on hardened where the test hit a fork limit,
or where there was prelink breaking glib C

#   Failed test 'PF_INET echo localhost reply'
#   at t/Socket.t line 61.
# Connected to 127.0.0.1
#   Failed test 'PF_INET echo INADDR_LOOPBACK reply'
#   at t/Socket.t line 100.
# Looks like you failed 2 tests of 6.

^ Is your ifconfig broken?


#   Failed test at t/510_ping_udp.t line 25.
#          got: '0'
#     expected: '1'
# Looks like you failed 1 test of 2.

More network weirdness.


But I kinda have seen these sorts of network tests bail before on hardened, just nailing down why and whos' responsibility it is to fix it is hard :/
Comment 3 Andreas K. Hüttel archtester gentoo-dev 2017-03-11 22:05:39 UTC

*** This bug has been marked as a duplicate of bug 519994 ***