Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Perl Module Template Error ???

posted by Krow on 07:55 AM May 3rd, 2002   Printer-friendly   Email story
When installing the Template module with the CPAN installer I get the following error

t/dbi.t...... ok 58/63 Failed 59 did not match expected
t/dbi.t...... ok 60/63 Failed 61 did not match expected
t/dbi.t...... ok 62/63 Failed 63 did not match expected

--
OhItsTrue

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • krow may correct me if I'm wrong, but I believe it's safe to skip the DBI test since Slash doesn't use anything that it tests anyway.
    --
    --Larry
  • I had a similar experience a few weeks ago, but I've been too busy to submit the bug report [cpan.org]. I don't use that part of it myself (and neither does Slashdot as the other poster stated).
  • This is a known problem with the test suite in Template Toolkit.

    Tatsuhiko Miyagawa found it and patched it on the Template list: http://www.template-toolkit.org/pipermail/template s/2002-April/003150.html [template-toolkit.org]

    I think Andy patched the CVS version, but it's probably safe just to skip the DBI tests.

    • I think Andy patched the CVS version, but it's probably safe just to skip the DBI tests.

      I hope they move this into CPAN soon. One of the biggest things that annoys perl users is stuff trying to be installed with CPAN.pm puking like this. I've seen module authors take eight months to take patches like the above and put a new version out on CPAN.

      • Normally it's not that long between releases. Andy likes to release interim developer releases (releases that you can download from the tt2.org website, but not for the CPAN) so various people can test out the changes on various platforms.

        The rationalle behind this is that quick releases to the CPAN could theoretically introduce much worse bugs that the ones that were originally patched, and by having people test the developers' releases he ensures that we get less showstopping bugs.