Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 348906 Details for
Bug 470996
perl-core/File-Path-2.90.0 fails tests
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build log
build.log (text/plain), 3.44 KB, created by
Michael Palimaka (kensington)
on 2013-05-22 12:39:58 UTC
(
hide
)
Description:
build log
Filename:
MIME Type:
Creator:
Michael Palimaka (kensington)
Created:
2013-05-22 12:39:58 UTC
Size:
3.44 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: perl-core/File-Path-2.90.0 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: perl@gentoo.org >[32;01m * [39;49;00mUSE: amd64 elibc_glibc kernel_linux userland_GNU >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox splitdebug test >>>> Unpacking source... >>>> Unpacking File-Path-2.09.tar.gz to /var/tmp/portage/perl-core/File-Path-2.90.0/work >>>> Source unpacked in /var/tmp/portage/perl-core/File-Path-2.90.0/work >>>> Preparing source in /var/tmp/portage/perl-core/File-Path-2.90.0/work/File-Path-2.09 ... >>>> Source prepared. >>>> Configuring source in /var/tmp/portage/perl-core/File-Path-2.90.0/work/File-Path-2.09 ... > [32;01m*[0m Using ExtUtils::MakeMaker > [32;01m*[0m perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLMAN3DIR=none DESTDIR=/var/tmp/portage/perl-core/File-Path-2.90.0/image/ >Checking if your kit is complete... >Looks good >Writing Makefile for File::Path >Writing MYMETA.yml and MYMETA.json >>>> Source configured. >>>> Compiling source in /var/tmp/portage/perl-core/File-Path-2.90.0/work/File-Path-2.09 ... > [32;01m*[0m emake OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu >make -j4 'OTHERLDFLAGS=-Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu' >cp Path.pm blib/lib/File/Path.pm >>>> Source compiled. >make -j4 test TEST_VERBOSE=0 >PERL_DL_NONLAZY=1 /usr/bin/perl5.16.3 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t >t/Path.t ... t/Path.t ... 1/129 ># Failed test 'created a directory not owned by nobodz:nobodz...' ># at t/Path.t line 503. ># STDERR: ># unable to map nobodz to a uid, ownership not changed: at t/Path.t line 501. ># unable to map nobodz to a gid, group ownership not changed: at t/Path.t line 501. ># ># doesn't match: ># (?^:\Aunable to map nobodz to a uid, ownership not changed: .* at \S+ line \d+ ># unable to map nobodz to a gid, group ownership not changed: .* at \S+ line \d+\b) ># as expected ># Looks like you failed 1 test of 129. > t/Path.t ... Dubious, test returned 1 (wstat 256, 0x100) >Failed 1/129 subtests > (less 29 skipped subtests: 99 okay) >t/pod.t .... t/pod.t .... skipped: PERL_AUTHOR_TESTING environment variable not set (or zero) >t/taint.t .. t/taint.t .. 1/6 t/taint.t .. ok > >Test Summary Report >------------------- >t/Path.t (Wstat: 256 Tests: 129 Failed: 1) > Failed test: 96 > Non-zero exit status: 1 >Files=3, Tests=135, 0 wallclock secs ( 0.03 usr 0.02 sys + 0.12 cusr 0.02 csys = 0.19 CPU) >Result: FAIL >Failed 1/3 test programs. 1/135 subtests failed. >make: *** [test_dynamic] Error 255 > [31;01m*[0m ERROR: perl-core/File-Path-2.90.0 failed (test phase): > [31;01m*[0m emake failed > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=perl-core/File-Path-2.90.0'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=perl-core/File-Path-2.90.0'`. > [31;01m*[0m The complete build log is located at '/var/log/portage/build/perl-core/File-Path-2.90.0:20130522-123309.log'. > [31;01m*[0m For convenience, a symlink to the build log is located at '/var/tmp/portage/perl-core/File-Path-2.90.0/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/perl-core/File-Path-2.90.0/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/perl-core/File-Path-2.90.0/work/File-Path-2.09' > [31;01m*[0m S: '/var/tmp/portage/perl-core/File-Path-2.90.0/work/File-Path-2.09'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 470996
: 348906