Bug #30740 for Test-Harness: print to STDERR in .t file no longer visible during make test

Wed Nov 14 16:51:34 2007 siracusa [...] gmail.com - Ticket created

Subject:

print to STDERR in .t file no longer visible during make test

Back in version 2.64, a print to STDERR in a .t file would show up when running make test. In 3.01, these prints seem to be eaten and no output appears. I rely on this output to issue warnings and explanations at the start of the testing process. Any way to get this feature back?

Wed Nov 14 17:02:00 2007 andy [...] hexten.net - Correspondence added

On Wed Nov 14 16:51:34 2007, JSIRACUSA wrote: Show quoted text

> Back in version 2.64, a print to STDERR in a .t file would show up > when running make test. In > 3.01, these prints seem to be eaten and no output appears. I rely on > this output to issue > warnings and explanations at the start of the testing process. Any > way to get this feature back?

You should still be seeing anything that goes to STDERR. Does your make test just do the normal ExtUtils::MakeMaker stuff?

Wed Nov 14 17:02:02 2007 The RT System itself - Status changed from 'new' to 'open'

Wed Nov 14 17:18:49 2007 siracusa [...] gmail.com - Correspondence added

From:

siracusa [...] gmail.com

On Wed Nov 14 17:02:00 2007, ANDYA wrote: Show quoted text

> You should still be seeing anything that goes to STDERR. Does your > make test just do the normal ExtUtils::MakeMaker stuff?

As far as I know. Check out Rose::DB from CPAN (for example) and see how the t/00-warning.t test doesn't print anything with 3.01 installed, but does with 2.64.

Wed Nov 14 21:49:39 2007 andy [...] hexten.net - Correspondence added

On Wed Nov 14 17:18:49 2007, JSIRACUSA wrote: Show quoted text

> On Wed Nov 14 17:02:00 2007, ANDYA wrote:

> > You should still be seeing anything that goes to STDERR. Does your > > make test just do the normal ExtUtils::MakeMaker stuff?

> > As far as I know. Check out Rose::DB from CPAN (for example) and see > how the t/00-warning.t test doesn't print anything with 3.01 installed, > but does with 2.64.

Ah yes. I see the problem. I suspect it's a buffering issue. I simulated your case with a simple test that outputs some diagnostics on STDERR, waits a few seconds then outputs test results on STDOUT. I don't see any output until the test completes. I'll attempt to come up with a solution for you - which may involve a new release of Test::Harness. Thanks for the report.

Wed Nov 14 21:49:46 2007 andy [...] hexten.net - Given to ANDYA

Thu Nov 15 16:42:21 2007 andy [...] hexten.net - Correspondence added

I've found and fixed the problem, thanks. It'll be fixed in the next release (3.02). In the mean time you can grab the latest version from http://svn.hexten.net/tapx/trunk Or can download a tarball of the latest build from http://hexten.net/tapx/ Thanks for the report :)

Thu Nov 15 16:42:23 2007 andy [...] hexten.net - Status changed from 'open' to 'resolved'