public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Munipradeep Beerakam <mpradeep@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH]get_mempolicy01: fix for changing failure due to	configuration error
Date: Thu, 18 Jun 2009 23:01:27 +0530	[thread overview]
Message-ID: <1245346287.5041.32.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <1244618075.10778.4.camel@munipradeep-laptop>

Hi Muni,

On Wed, 2009-06-10 at 12:44 +0530, Munipradeep Beerakam wrote:
> Hi,
> 
> Here is the attachment to fix the configuration error in
> get_mempolicy01.c
> Actually it should not fail due to configuration error. So changed the
> necessary.
> 
> Thanks
> Muni
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> differences
> between files
> attachment
> (get_mempolicy01.patch)
> 
> 
> ---
> a/testcases/kernel/syscalls/get_mempolicy/get_mempolicy01.c 2009-06-10
> 07:08:08.000000000 -0400
> +++
> b/testcases/kernel/syscalls/get_mempolicy/get_mempolicy01.c 2009-06-10
> 07:12:16.000000000 -0400
> @@ -296,7 +296,7 @@
>                          TEST(rc = syscall(__NR_set_mempolicy,
> tc->policy,&nodemask, maxnode));
> 
>                 if (TEST_RETURN < 0) {
> -                       tst_resm(TFAIL, "set_mempolicy() failed -
> errno = %d : %s",TEST_ERRNO, strerror(TEST_ERRNO));
> +                       tst_resm(TCONF, "set_mempolicy() failed -
> errno = %d : %s",TEST_ERRNO, strerror(TEST_ERRNO));
>                          result = 1;
>                         cleanup();
>                          tst_exit();
> @@ -307,7 +307,7 @@
>                  // mmap memory
>                  p = mmap(NULL, len, PROT_READ|PROT_WRITE,MAP_PRIVATE|
> MAP_ANONYMOUS, 0, 0);
>                  if (p == (void*)-1) {
> -                       tst_resm(TFAIL, "malloc failed - errno = %d :
> %s",TEST_ERRNO, strerror(TEST_ERRNO));
> +                       tst_resm(TCONF, "malloc failed - errno = %d :
> %s",TEST_ERRNO, strerror(TEST_ERRNO));
>                          result = 1;
>                         cleanup();
>                          tst_exit();

The problem reported on your machine is function not implemented.
However, if you change the FAIL to blindly CONF, that will cause issues
like actual failures reported wrongly.

See, whether you can find out ways to isolate only function not
implemented part.

Regards--
Subrata



------------------------------------------------------------------------------
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

  reply	other threads:[~2009-06-18 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  7:14 [LTP] [PATCH]get_mempolicy01: fix for changing failure due to configuration error Munipradeep Beerakam
2009-06-18 17:31 ` Subrata Modak [this message]
2009-06-19  8:55   ` Munipradeep Beerakam
2009-06-23 14:50     ` Subrata Modak
2009-06-23 16:06       ` Jiri Palecek
2009-06-25  9:10         ` 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=1245346287.5041.32.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --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