On 01/29/2013 01:48 PM, John H. Embretsen wrote:
> I tried the same on a machine without Log4perl and I see that all output
> from ErrorLogAlarm reporter is missing, both print() and say() calls.
> This happens only with runall.pl (or runall.pl via combinations.pl).
>
> When using runall-new.pl (or combinations.pl using --new option) all
> expected output is present.
>
> I don't know why this is happening...
The snippet:
Must ALWAYS be run. So it is the first thing in all scripts. And in all
base modules, e.g. lib/GenTest.pm. It is required that "use Gentest;"
comes before all "use GenTest::blabla...;" and that "use GenTest;" is in
ALL subclasses (recursively) of GenTest.
Might be a hint to why it does not work (don't know if this is the case
though)
On 01/29/2013 01:48 PM, John H. Embretsen wrote:
> I tried the same on a machine without Log4perl and I see that all output
> from ErrorLogAlarm reporter is missing, both print() and say() calls.
> This happens only with runall.pl (or runall.pl via combinations.pl).
>
> When using runall-new.pl (or combinations.pl using --new option) all
> expected output is present.
>
> I don't know why this is happening...
The snippet:
my $logger; :Log4perl- >import( ); >get_logger( 'randgen. gentest' );
eval
{
require Log::Log4perl;
Log:
$logger = Log::Log4perl-
};
Must ALWAYS be run. So it is the first thing in all scripts. And in all :blabla. ..;" and that "use GenTest;" is in
base modules, e.g. lib/GenTest.pm. It is required that "use Gentest;"
comes before all "use GenTest:
ALL subclasses (recursively) of GenTest.
Might be a hint to why it does not work (don't know if this is the case
though)
Bernt