httpd-test-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Benson <gben...@redhat.com>
Subject Re: Core dump scan breaks exit() status
Date Wed, 29 Aug 2001 14:45:45 GMT

On Wed, 29 Aug 2001, Stas Bekman wrote:

> On Wed, 29 Aug 2001, Gary Benson wrote:
>
> >
> > Hi all,
> >
> > The core dump scanning bit in TestRun::install_sighandlers overwrites the
> > exit status, making t/TEST always return 0. This isn't too great if you
> > are calling it from a script ;-)
> >
> > I'm not interested in fixing it -- I've got a bunch of c-modules to port
> > ;-) -- but here's my take on the problem:
> >
> > The change was made in revision 1.28 of TestRun.pm, if you want to have a
> > look at it yourself. I have no idea how to fix this in a nice way, short
> > of moving it into a wrapper that runs t/TEST, remembers the exit status,
> > then checks for coredumps afterwards and then exits accordingly.
>
> I guess you are talking about the END block:
>
>     eval "END {
>              eval {
>                 Apache::TestRun->new(test_config =>
>                                      Apache::TestConfig->thaw)->scan;
>              };
>          }";
>
> but what exit status was it returning before? I don't think we have any
> definition of the exit status definitions according to the tests success
> or failure. Or do we?

At the moment (or at least before that END block was there) it returns 1
if something breaks.


Mime
View raw message