All of lore.kernel.org
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: ltp-list@lists.sourceforge.net, Mike Frysinger <vapier@gentoo.org>
Subject: Re: [LTP] LTP Build - Would it be possible to handle testcase	build failures without failing all the build process?
Date: Mon, 06 Jul 2009 21:21:04 +0530	[thread overview]
Message-ID: <1246895464.4887.55.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <200907060426.57132.vapier@gentoo.org>

On Mon, 2009-07-06 at 04:26 -0400, Mike Frysinger wrote: 
> On Monday 06 July 2009 03:07:56 Lucas Meneghel Rodrigues wrote:
> > LTP does have a large amount of testcases, and most of the testcases are
> > independent from each other, thus IMHO, a single compilation failure
> > should not fail the whole build process, instead, the tests that could
> > not be compiled should be marked as BROKEN, and should not be executed
> > during LTP execution.

Yes, that would be great. And for that an m4 rule file has to be written
for each and every LTP test, checking:
1) Header dependency,
2) Library dependency, etc
before compiling.

Regards--
Subrata

> >
> > Do we have any plans to handle individual build failures in a way that
> > doesn't fail the whole build process?
> 
> use the -k option with make
> -mike
> ------------------------------------------------------------------------------
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2009-07-06 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  7:07 [LTP] LTP Build - Would it be possible to handle testcase build failures without failing all the build process? Lucas Meneghel Rodrigues
2009-07-06  8:26 ` Mike Frysinger
2009-07-06 15:51   ` Subrata Modak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1246895464.4887.55.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=lmr@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.