Re: pkg/51903

["David H. Gutteridge" <dhgutteridge%sympatico.ca@localhost>]

The following reply was made to PR pkg/51903; it has been noted by GNATS.

From: "David H. Gutteridge" <dhgutteridge%sympatico.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/51903
Date: Sun, 22 Jan 2017 12:26:04 -0500

 On Sun, 2017-01-22 at 16:30 +0000, coypu%SDF.ORG@localhost wrote:
 > 
 > Â No, disabling PaX & ASLR doesn't help.
 > Â It's also complaining before the segfault:
 > Â 
 > Â ===> Testing for p5-XML-Sablotron-1.01nb6
 > Â Manifying 2 pod documents
 > Â Running Mkbootstrap for XML::Sablotron ()
 > Â chmod 644 "Sablotron.bs"
 > Â PERL_DL_NONLAZY=1 "/home/pkg/pkg/bin/perl" "-MExtUtils::Command::MM" 
 > "-MTest::Harness" "-e" "undef *Test::Harness::Switches;
 > test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
 >  t/dom.t ......... Failed 1/39 subtests 
 >  t/domHandler.t .. Failed 3/4 subtests 
 >  t/sablot.t ...... Failed 3/10 subtests 
 > Â 
 > Â Test Summary Report
 > Â -------------------
 >  t/dom.t       (Wstat: 139 Tests: 38 Failed: 0)
 > Â Â Â Non-zero wait status: 139
 >    Parse errors: Bad plan.  You planned 39 tests but ran 38.
 > Â t/domHandler.t (Wstat: 139 Tests: 1 Failed: 0)
 > Â Â Â Non-zero wait status: 139
 >    Parse errors: Bad plan.  You planned 4 tests but ran 1.
 >  t/sablot.t    (Wstat: 139 Tests: 7 Failed: 0)
 > Â Â Â Non-zero wait status: 139
 >    Parse errors: Bad plan.  You planned 10 tests but ran 7.
 >  Files=3, Tests=46,  0 wallclock secs ( 0.01 usr  0.02 sys +  0.03
 > cusr  0.04 csys =  0.10 CPU)
 > Â Result: FAIL
 > Â Failed 3/3 test programs. 0/46 subtests failed.
 > Â *** Error code 255
 
 Each of those test scripts generates a distinct segfault, that's why
 the test target is noting fewer sub-test completions than expected for
 all of them. The perl.core file gets overwritten as each test script
 runs and faults.
 
 Thanks for checking on another OS, that was one of the things I was
 wondering about, because I'm working on a package that optionally
 depends on this one, and I wasn't sure if it was worth offering that
 choice. It seems it is (though not as the default, at least at
 present).