I'm taking a stab at setting up slashcode, and I'm absolutely stumped. I'm trying to install HTML::Parser, and I keep getting failed tests. It's a fresh installation of Red Hat Linux 8.0 with perl 5.8.0 and I think I've got all the prerequisites installed. Normally, I wouldn't freak out too much about a failed test or two, but the final output (make: *** [test_dynamic] Error 29) is worrysome. I tried running make install from there and everything looked ok, but I wonder if this is going to come back and bite me later.

Here's the output from make test:

[zim HTML-Parser-3.28]# make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_h +arness(0, 'blib/lib', 'blib/arch')" t/*.t t/api_version........ok t/argspec-bad........ok t/argspec............ok t/argspec2...........ok t/attr-encoded.......ok t/callback...........ok t/case-sensitive.....ok t/cases..............ok t/comment............ok t/crashme............ok t/declaration........ok t/default............ok t/dtext..............ok t/entities...........Malformed UTF-8 character (unexpected non-continu +ation byte 0x72, immediately after start byte 0xe5) in substitution i +terator. t/entities...........ok 2/11Confused test output: test 2 answered afte +r test 4 t/entities...........ok 3/11Confused test output: test 3 answered afte +r test 5 t/entities...........NOK 4Confused test output: test 4 answered after +test 6 t/entities...........NOK 5Confused test output: test 5 answered after +test 7 t/entities...........NOK 6Confused test output: test 6 answered after +test 8 t/entities...........ok 7/11Confused test output: test 7 answered afte +r test 9 t/entities...........ok 8/11Confused test output: test 8 answered afte +r test 10 t/entities...........FAILED tests 1-3, 7-9 Failed 6/11 tests, 45.45% okay t/entities2..........ok t/filter-methods.....ok t/filter.............ok t/handler-eof........ok t/handler............ok t/headparser-http....ok t/headparser.........FAILED test 3 Failed 1/4 tests, 75.00% okay t/ignore.............ok t/largetags..........ok t/linkextor-base.....ok t/linkextor-rel......ok t/magic..............ok t/marked-sect........ok t/offset.............ok t/options............ok t/parsefile..........ok t/parser.............ok t/plaintext..........ok t/process............ok t/pullparser.........ok t/skipped-text.......ok t/textarea...........ok t/tokeparser.........ok t/uentities..........FAILED tests 2, 8 Failed 2/10 tests, 80.00% okay t/unbroken-text......ok t/xml-mode...........ok Failed Test Stat Wstat Total Fail Failed List of Failed ---------------------------------------------------------------------- +--------- t/entities.t 11 6 54.55% 1-3 7-9 t/headparser.t 4 1 25.00% 3 t/uentities.t 10 2 20.00% 2 8 Failed 3/40 test scripts, 92.50% okay. 9/236 subtests failed, 96.19% o +kay. make: *** [test_dynamic] Error 29
-Logan
"What do I want? I'm an American. I want more."

In reply to Failed Tests while Installing HTML::Parser by logan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.