From: "Mitani" <mitani@ryobi.co.jp>
To: 'Garrett Cooper' <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] rt_sigaction{02-03} tests validation
Date: Wed, 10 Feb 2010 10:21:14 +0900 [thread overview]
Message-ID: <000001caa9ef$56c61360$04523a20$@co.jp> (raw)
In-Reply-To: <364299f41002010046r315a6609xa3f4afd838cf0215@mail.gmail.com>
> -----Original Message-----
> From: Garrett Cooper [mailto:yanegomi@gmail.com]
> Sent: Monday, February 01, 2010 5:46 PM
> To: Mitani
> Cc: ltp-list@lists.sourceforge.net
> Subject: Re: [LTP] rt_sigaction{02-03} tests validation
>
> On Mon, Feb 1, 2010 at 12:31 AM, Mitani <mitani@ryobi.co.jp> wrote:
> > Hi,
> >
> > I understood that rt_sigaction01, rt_sigprocmask01 and rt_sigsuspend01
> > tests failure is architecture(x86_64) specific issues.
> > Sorry, I don't know how do I fix it, yet.
> >
> > But when I examined these issues, I noticed that rt_sigaction's test
> > also has rt_sigaction{02-03} tests.
> > Currently, rt_sigaction{02-03} are not run.
> > I think that it's also necessary to run rt_sigaction{02-03} tests
> > because rt_sigaction01 test well running at x86 architecture.
> > How about add rt_sigaction{02-03} to the test case?
> >
> > If "./runtest/syscalls" is fixed, these tests succeed as follows:
> >
> > ------------
> >
> > Test Start Time: Mon Feb 1 16:38:37 2010
> > -----------------------------------------
> > Testcase Result Exit Value
> > -------- ------ ----------
> > rt_sigaction01 PASS 0
> > rt_sigaction02 PASS 0
> > rt_sigaction03 PASS 0
> > -----------------------------------------------
> > Total Tests: 3
> > Total Failures: 0
> > Kernel Version: 2.6.18-164.el5
> > Machine Architecture: i686
> > Hostname: 5-4.localdomain
> >
> > ------------
> >
> > Index:
> > ./runtest/syscalls
> > ============
> > --- runtest/syscalls.org 2009-12-16 04:32:18.000000000 +0900
> > +++ runtest/syscalls 2010-02-01 16:48:43.000000000 +0900
> > @@ -801,6 +801,8 @@
> > rmdir05 rmdir05
> >
> > rt_sigaction01 rt_sigaction01
> > +rt_sigaction02 rt_sigaction02
> > +rt_sigaction03 rt_sigaction03
> > rt_sigprocmask01 rt_sigprocmask01
> > rt_sigprocmask02 rt_sigprocmask02
> > rt_sigqueueinfo01 rt_sigqueueinfo01
> > ============
>
> Sounds like a plan. Will be committed in a few mins.
> Thanks!
> -Garrett
Hi, Garrett,
I tested it in x86 systems, but it seems still not fixed yet.
Is there some problems?
If it needs further revision, I'm glad when I get your help.
I'm sorry for troubling you when you are busy.
Thank you--
-Tomonori Mitani
------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-02-10 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 8:31 [LTP] rt_sigaction{02-03} tests validation Mitani
2010-02-01 8:46 ` Garrett Cooper
2010-02-10 1:21 ` Mitani [this message]
2010-02-10 1:28 ` Garrett Cooper
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='000001caa9ef$56c61360$04523a20$@co.jp' \
--to=mitani@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.net \
--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