On 1/16/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > t/threaded....dubious
> > Test returned status 5 (wstat 1280, 0x500)
> > DIED. FAILED tests 4-14
That seems to be a clean exit(5) rather than an crash.
Are you (Steffen I think) able to get long test output running that one by
hand?
I think the Perl running in a subshell from the Harness is the one
that segfaults, but Test::Harness somehow still reports that status 5
with the same wstat:
C:\DOCUME~1\David\LOCALS~1\Temp\cpan\build\Tie-RefHash-1.35>dmake test
TEST_VERBOSE=1 TEST_FILES=t\threaded.t
C:\perl\perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(1, 'blib\
lib', 'blib\arch')" t\threaded.t
t\threaded....1..14
ok - fetch by string before clone (foo)
ok - fetch by ref before clone (HASH(0xb01754))
ok - fetch by ref before clone (ARRAY(0xb01760))
dubious
Test returned status 5 (wstat 1280, 0x500)
DIED. FAILED tests 4-14
Failed 11/14 tests, 21.43% okay
Failed Test Stat Wstat Total Fail List of Failed
-------------------------------------------------------------------------------
t\threaded.t 5 1280 14 22 4-14
Failed 1/1 test scripts. 11/14 subtests failed.
Files=1, Tests=14, 44 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 CPU)
Failed 1/1 test programs. 11/14 subtests failed.
dmake: Error code 133, while making 'test_dynamic'
