[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to change the behaviour of "make check"?

From: Ireneusz SZCZESNIAK
Subject: Re: how to change the behaviour of "make check"?
Date: Wed, 17 Sep 2003 11:28:44 -0600 (MDT)


Thanks for your e-mail.

bernd> It should if you say "make -k check".

"make -k check" only partially works for me.  The "-k" option causes
"make" to ignore all errors and therefore continue with recursive
execution -- in this way it does what I want.

But I only want "make" to ignore errors from running tests, not all
errors.  My test scripts are automatically generated by "make" and
then run.  If "make" fails to generate such a script, then I want
"make" to report the error and stop.


On Tue, 16 Sep 2003, Bernd Jendrissek wrote:

> Hash: SHA1
> On Mon, Sep 15, 2003 at 05:18:11PM -0600, Ireneusz SZCZESNIAK wrote:
> > Let me explain the problem further.  In my software package there is
> > the directory "tests", which contains subdirectories "A" and "B".
> > Each of the subdirectories "A" and "B" contains some tests.  When a
> > test in the directory "A" fails (error code 1), then "make check"
> > reports an error, exits, and therefore does not execute tests in the
> > directory "B", while I want "make check" to run the tests also in the
> > directory "B".
> It should if you say "make -k check".
> - --
> [I can't guarantee the integrity of my mail; I suspect my employer of
> mail tampering (adding disclaimers without my authorization).  Please
> consider only signed text as my words.  Verify if you can!]
> "There are few or no amazing magicians in the world. Precious few
> people are skilled enough to walk in on the blazing ruins of an
> arbitrary sinking project, patch the holes and make it into a graceful
> ocean liner. People that have this skill ought to be designing
> projects correctly from the ground up, not dousing the flames of
> someone else's train wreck."
>    - Lewin Edwards (comp.arch.embedded)
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see
> iD8DBQE/Zrn//FmLrNfLpjMRAtDKAJ0UWU72FcV3zb7H4ct1ZHTXPaff7ACfTmzS
> jJJ0mnQyEWDAJGRm1r6l3qk=
> =4Ntq

reply via email to

[Prev in Thread] Current Thread [Next in Thread]