From: Mike Frysinger <vapier@gentoo.org>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] LTP Build - Would it be possible to handle testcase build failures without failing all the build process?
Date: Mon, 6 Jul 2009 04:26:56 -0400 [thread overview]
Message-ID: <200907060426.57132.vapier@gentoo.org> (raw)
In-Reply-To: <1246864076.2865.35.camel@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
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.
>
> 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
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 79 bytes --]
------------------------------------------------------------------------------
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-06 8:27 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 [this message]
2009-07-06 15:51 ` Subrata Modak
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=200907060426.57132.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=ltp-list@lists.sourceforge.net \
/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.