From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fix UNRESOLVED failures of pthread tests in open_posix_testsuite
Date: Mon, 07 Sep 2009 17:09:52 +0530 [thread overview]
Message-ID: <1252323604.4922.26.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <4AA06ECF.4040508@jp.fujitsu.com>
On Fri, 2009-09-04 at 10:35 +0900, Seiichi Ikarashi wrote:
> Hi,
>
> I report a couple of "UNRESOLVED" failures of open_posix_testsuite in ltp
> and send a patch for them.
>
> I got following failures while executing open_posix_testsuite.
>
> > conformance/interfaces/pthread_setschedparam/5-1: execution: UNRESOLVED: Output:
> > [07:16:29]Test conformance/interfaces/pthread_setschedparam/5-1.c unresolved: got 22 (Invalid argument) on line 152 (Sem_post in signal handler 1)
>
> > conformance/interfaces/pthread_detach/4-3: execution: UNRESOLVED: Output:
> > *snip*
> > [12:05:38]Test conformance/interfaces/pthread_detach/4-3.c unresolved: got 22 (Invalid argument) on line 157 (Sem_post in signal handler 1)
>
> Both of them have wrong steps of its test preparation:
> 1. register signal handlers (just do sem_post()) for SIGUSR1/SIGUSR2.
> 2. block those signals
> 3. prepare something (sem_init()) for these signal handlers
> 4. send signals to itself from sub-threads.
>
> They have a window of not-yet-prepared-for-signals
> between step 1 and 2. I think above "UNRESOLVED" failures
> (sem_post() before sem_init()) are the result of getting a
> signal during this window.
> I don't know who sent a signal to them but I guess
> neighboring tests are suspects, because number of tests run
> concurrently in open_posix_testsuite.
>
> The fix shall be just delaying step 1 to between step 2 and 4,
> so I wrote such a patch for both pthread_setschedparam and
> pthread_detach. I have confirmed that this UNRESOLVED failure
> disappeared with this patch applied.
>
> Signed-off-by: Seiichi Ikarashi <s.ikarashi@jp.fujitsu.com>
Ok Thanks.
Regards--
Subrata
>
> Regards,
>
> ------------------------------------------------------------------------------
> 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
prev parent reply other threads:[~2009-09-07 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 1:35 [LTP] [PATCH] fix UNRESOLVED failures of pthread tests in open_posix_testsuite Seiichi Ikarashi
2009-09-07 11:39 ` Subrata Modak [this message]
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=1252323604.4922.26.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=s.ikarashi@jp.fujitsu.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