public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>, Henry Yei <hyei@mvista.com>
Cc: ltp-list <ltp-list@lists.sf.net>, rohit verma <rohit.170309@gmail.com>
Subject: Re: [LTP] [PATCH] Issue with rt_sigqueueinfo testcase in LTP.
Date: Fri, 07 Aug 2009 18:11:55 +0530	[thread overview]
Message-ID: <1249648916.4851.45.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <364299f40908061921i39ad3e51q4aeffc666166c496@mail.gmail.com>

On Thu, 2009-08-06 at 19:21 -0700, Garrett Cooper wrote: 
> On Thu, Aug 6, 2009 at 5:50 PM, Henry Yei<hyei@mvista.com> wrote:
> > Yes, I had just noticed this as well.  Since it was "passing", it took awhile to spot.
> >
> > Returning pass even with tst_resm(TFAIL,.. Being called must have something to do with the forking, but I'm not familiar with how the LTP framework deals with that.
> 
> I don't think that's the problem. I think that the real problem is how

The part of the problem is how and when are setup() and cleanup()s are
handled.

> the testcase itself is written, because I don't see any code that
> checks WIFEXITED and WIFSIGNALED (I would check for both those items
> when doing sigqueue), and I don't see where the child(ren) actually

Can you just add them up when you find time. Meanwhile i am checking in
Henryś patch. Thanks.

Regards--
Subrata

> exit... HMMM...
> 
> Thoughts?
> -Garrett
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-08-07 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d51f89b0908032310k20c3843am7ea069d03436a7a@mail.gmail.com>
     [not found] ` <1249387637.15587.29.camel@subratamodak.linux.ibm.com>
2009-08-04 12:16   ` [LTP] Issue with rt_sigqueueinfo testcase in LTP rohit verma
2009-08-06  9:10     ` Michal Simek
2009-08-07  0:50       ` [LTP] [PATCH] " Henry Yei
2009-08-07  2:21         ` Garrett Cooper
2009-08-07 12:41           ` Subrata Modak [this message]
2009-08-14  6:55             ` rohit verma
2009-08-14 18:39               ` Henry Yei

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=1249648916.4851.45.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=hyei@mvista.com \
    --cc=ltp-list@lists.sf.net \
    --cc=rohit.170309@gmail.com \
    --cc=yanegomi@gmail.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