From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Munipradeep Beerakam <mpradeep@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net, Jiri Palecek <jpalecek@web.de>,
iranna.ankad@in.ibm.com
Subject: Re: [LTP] Some of the testcases which are resulting in FAIL even though they might not be
Date: Thu, 18 Jun 2009 23:01:38 +0530 [thread overview]
Message-ID: <1245346298.5041.35.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <200906121408.15925.jpalecek@web.de>
On Fri, 2009-06-12 at 14:08 +0200, Jiri Palecek wrote:
> On Wednesday 10 June 2009 14:06:25 Munipradeep Beerakam wrote:
> > Hi,
>
> Hi,
>
> > Here is the list of testcases in May 2009 LTP, which *may* result in
> > FAIL even though it is a configuration error, not the error due to the
> > functionality we are testing. Those tests should give "CONF" message,
> > not "FAIL". I ran LTP on 2.6.18 kernel, x86 architecture.
> >
> >
> > 3. get_mempolicy01
> > Part of code, which is not correct
> > tst_resm(TFAIL, "set_mempolicy() failed - errno = %d : %s",TEST_ERRNO,
> > strerror(TEST_ERRNO));
> > ...
> > ...
> > tst_resm(TFAIL, "malloc failed - errno = %d : %s",TEST_ERRNO,
> > strerror(TEST_ERRNO));
> >
> > 4. mq_open01
> > Part of code, which is not correct
> > if (TEST_RETURN < 0) {
> > tst_resm(TFAIL, "mq_getsetattr failed - errno =
> > %d : %s",TEST_ERRNO, strerror(TEST_ERRNO));
>
> Not that I'd say this code is stellar, it may even be incorrect, but changing these to TCONF wouldn't be correct either. These error messages should be TCONF only if errno is ENOSYS, otherwise, they should be reported as TBROK, because it would be an error that prevents the test to run. The best option, however, would probably be to add a tst_kvercmp check for kernel versions that contain the respective functions.
>
Muni,
Can you work out a patch on this lines. I would help you to do so if
required.
Regards--
Subrata
> Regards
> Jiri Palecek
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-18 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 12:06 [LTP] Some of the testcases which are resulting in FAIL even though they might not be Munipradeep Beerakam
2009-06-12 12:08 ` Jiri Palecek
2009-06-18 17:31 ` Subrata Modak [this message]
2009-06-18 17:31 ` Subrata Modak
2009-06-30 10:04 ` Pradeep K Surisetty
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=1245346298.5041.35.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=iranna.ankad@in.ibm.com \
--cc=jpalecek@web.de \
--cc=ltp-list@lists.sourceforge.net \
--cc=mpradeep@linux.vnet.ibm.com \
/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