From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: LTP <ltp-list@lists.sourceforge.net>
Subject: [LTP] LTP Build - Would it be possible to handle testcase build failures without failing all the build process?
Date: Mon, 06 Jul 2009 04:07:56 -0300 [thread overview]
Message-ID: <1246864076.2865.35.camel@localhost.localdomain> (raw)
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?
Thanks for your attention!
Lucas
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-07-06 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 7:07 Lucas Meneghel Rodrigues [this message]
2009-07-06 8:26 ` [LTP] LTP Build - Would it be possible to handle testcase build failures without failing all the build process? Mike Frysinger
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=1246864076.2865.35.camel@localhost.localdomain \
--to=lmr@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox