Also, standard TAP would emit

1..1
[download]

dmake test TEST_VERBOSE=1
[download]

#!perl -w
use strict;
warn "\nstrict.pm loaded\n";
my $LOG;
my $LOG_FILE = './test_log';
warn "\nvariables declared\n";
.... and so on
[download]

Hi Rob,

like i mentioned when I posted this question any output of the script itself is discharged by the TEST::HARNESS module!.
So also the warnings!
Thats is why I output to a log and write some informations to check if the script runs.
It looks that is runs o.k, but I have no idea if it exits or not. When it does not exit the pove or TEST::HARNESS can not proceed and will hang.
I need to understand who the control gets back to the module that calls my script when I do either a prove or a make test.
WolliK

Hi Rob,
the situation is the same either with or without the TEST_VERBOSE option is set.
WolliK

I put your 00_simple_test.t script into t directory on my Ubuntu and running "prove -v" did not hang. Could you, please, try to put the following into 00_simple_test.t and post the results of prove -v?

#!/usr/bin/perl -w
use strict;
use Test::More qw( no_plan );
ok(1);
[download]

Next, if you insist on using "make test" for your testing, could you please post the Makefile as choroba has requested? Thanks!

Hi hotpelmen,
this outpout was produces by a:
"make test TEST_VERBOSE=1" on the shell.
When I try to run it as a perl inliner I got the folloing:


perl -MExtUtils::Command::MM -MTest::Harness - e undef *Test::Har
ness::Switches; test_harness(1, 'blib/lib', 'blib/arch') t/ *.t
/bin/-sh: syntax error: `(' unexpected
[download]

But I have no idea how to start it manualy or how to use the correct syntax for the perl interpreter?
Can you help me on this ?

The log with "### START ##..." was the outout of the test script: 00simple_test.t that I'v created to see what is going on since the TEST::HARNESS will discharge any output to STDOUT.


I've found this on the internet:
"make test TEST_VERBOSE=1 TEST_FILE=<test_script> | tee test.log"
when I run it as:
"make test TEST_VERBOSE=1 TEST_FILE=t/00simple_test.t | tee test.log"
It also hangs and there are no additional informations in the created test.log. Did someone know what additional TEST variables I can use to see what is going on ?


Regards WolliK

Shouldn't you be able to run prove -bv? Then you don't have to fiddle with the harness directly. If it runs as it should, then your problem is probably something in the makefile. If it doesn't run as it should, the error messages might be more helpful at least.




Dave

perl -MExtUtils::Command::MM -MTest::Harness - e undef *Test::Harness:
+:Switches; test_harness1, 'blib/lib', 'blib/arch') t/ *.t
/bin/-sh: syntax error: `(' unexpected
[download]

I think the problem there is the space in - e, which should be appearing as -e

Remove that space and at least one of your problems should go away.
However, I don't know exactly where to look in order to fix whatever it is that's inserting that space - somewhere in ExtUtils::MakeMaker, I guess.
What version of EU::MM do you have ?

Update: On closer inspection it seems that you might be responsible for the insertion of that space - as the space aint there in your first post.

Cheers,
Rob

#!/usr/bin/perl

BEGIN {
    $ENV{'HARNESS_ACTIVE'}  = 1;
    $ENV{'HARNESS_VERBOSE'} = 1;
}

use strict;
use warnings;
use Test::More tests => 1;

my $log_file = './test_log';

my ( $sec, $min, $hour, $mday, $mon, $year, $wday, $yday, $isdst )
    = localtime(time);

my $timestamp = sprintf(
    "%4d-%02d-%02d %02d:%02d:%02d",
    $year + 1900,
    $mon + 1, $mday, $hour, $min, $sec
);

open( OUT, '>', $log_file )
    or die "Could not open OUT! $!\n";
binmode OUT, ":encoding(UTF-8)";

print OUT "### START##################################################
+##\n";
print OUT "\t $timestamp  \n";

ok 1, "running the test $0...";
print OUT "ok 1 - running the test $0";

close(OUT);
[download]

Here's the result, using perl:

###START####################################################
     2015-02-13 11:44:06  
ok 1 - running the test /root/Desktop/test_hangs.t.tdy
[download]

###START####################################################
     2015-02-13 11:22:31  
ok 1 - running the test /root/Desktop/test_hangs.t
[download]

Hi Khen1950fx,
it is not the script, ist is also not the prove scriptin /usr/bin, is is the APP:PROOVE witch calls some TAP functions that will not give the control back to my shell.
I've put some additional logging into the /usr/bin/prove script to see what happened. It:
- creates the $app
- processses the $app
- executes by running the app ($app->run)
- exits with the either 0 or 1 depending on the previous return value


The test script is fired up, runs and logs after the entries done by the prove run.

But the shell where I started the prove command just hangs and waits for ever even if the test script has finished successfull.
wollik

Have you tried to test with prove -v against just one little standard test script

#!/usr/bin/perl -w
use strict;
use Test::More qw( no_plan );
ok(1);
[download]

as described above to be sure that the test indeed finishes. Please do so and post the results.

Hi Khen1950fx,
What do you mean by using different break keys? I fond lots of ways to break out of the opertation and get my shell back, but all these results in quit messages, so the prove or make test routines will not proceed because of the break or quit return value.
wollik