in reply to Test::Harness and uninitialized value in eval

upgrade?
  • Comment on Re: Test::Harness and uninitialized value in eval

Replies are listed 'Best First'.
Re^2: Test::Harness and uninitialized value in eval
by AZed (Monk) on Nov 22, 2008 at 05:28 UTC

    Well, first off, I can't force someone else's smoke testing rig to be upgraded. That said, however, I can currently reproduce this on both of my own test boxes, and both are running Perl 5.10, and one has Test::Harness 3.14 dropped in on top of it. If I need to upgrade something, it's not clear what.

    (And yes, all tests actually pass on both of my own test boxes.)

      That said, however, I can currently reproduce this on both of my own test boxes

      You mean you can reproduce all of those warnings, but not the failures ?
      If you can reproduce all of those warnings, then hopefully you can also find a way of shutting them up, by placement of no warnings 'uninitialized'; in the appropriate place - probably in the test files. (Or you could just remove the use warnings; altogether.) Once you've managed to eradicate those warnings in your own environment, just release a devel build to CPAN, and then the testers' output won't be truncated and you'll be able to see where the failures are occurring.

      Obviously, this hinges on your being able to work out how to eradicate those warnings. Good luck !!

      Cheers,
      Rob