From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Jacky Malcles <Jacky.Malcles@bull.net>
Cc: ltp-list@lists.sourceforge.net, maknayak@in.ibm.com
Subject: Re: [LTP] clock_nanosleep01 TestCase FAIL --> is it known?
Date: Fri, 26 Jun 2009 17:03:18 +0530 [thread overview]
Message-ID: <1246015998.6196.25.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <4A4490B2.4070803@bull.net>
On Fri, 2009-06-26 at 11:11 +0200, Jacky Malcles wrote:
> is it a testcase issue? (because case05 ends with OK).
Not sure. A new entrant and that too blind port. Needs analysis.
Regards--
Subrata
> report:
> [root@xena3 clock_nanosleep]# ./clock_nanosleep01
> clock_nanosleep01 0 INFO : (case00) START
> clock_nanosleep01 0 INFO : check sleep time: (min:480) < 507 <
> (max:520) (msec)
> clock_nanosleep01 0 INFO : remain time: 191 5658608
> EXPECT: return value(ret)=0 errno=0 (Success), remain time check=OK
> RESULT: return value(ret)=0 errno=0 (Success), remain time check=NG
> clock_nanosleep01 0 INFO : (case00) END => NG
> clock_nanosleep01 0 INFO : (case01) START
> clock_nanosleep01 0 INFO : check sleep time: (min:480) < 509 <
> (max:520) (msec)
> clock_nanosleep01 0 INFO : remain time: 191 5658608
> EXPECT: return value(ret)=0 errno=0 (Success), remain time check=OK
> RESULT: return value(ret)=0 errno=0 (Success), remain time check=NG
> clock_nanosleep01 0 INFO : (case01) END => NG
> clock_nanosleep01 0 INFO : (case02) START
> clock_nanosleep01 0 INFO : remain time: 191 5658608
> EXPECT: return value(ret)=22 errno=0 (Success), remain time check=OK
> RESULT: return value(ret)=22 errno=0 (Success), remain time check=NG
> clock_nanosleep01 0 INFO : (case02) END => NG
> clock_nanosleep01 0 INFO : (case03) START
> clock_nanosleep01 0 INFO : remain time: 191 5658608
> EXPECT: return value(ret)=22 errno=0 (Success), remain time check=OK
> RESULT: return value(ret)=22 errno=0 (Success), remain time check=NG
> clock_nanosleep01 0 INFO : (case03) END => NG
> clock_nanosleep01 0 INFO : (case04) START
> clock_nanosleep01 0 INFO : remain time: 191 5658608
> EXPECT: return value(ret)=95 errno=0 (Success), remain time check=OK
> RESULT: return value(ret)=22 errno=0 (Success), remain time check=NG
> clock_nanosleep01 0 INFO : (case04) END => NG
> clock_nanosleep01 0 INFO : (case05) START
> clock_nanosleep01 0 INFO : remain time: 9 490280000
> EXPECT: return value(ret)=4 errno=0 (Success)
> RESULT: return value(ret)=4 errno=0 (Success)
> clock_nanosleep01 0 INFO : (case05) END => OK
> clock_nanosleep01 1 FAIL : clock_nanosleep01 failed - errno = 0 :
> Success
> clock_nanosleep01 0 INFO : NG
> [root@xena3 clock_nanosleep]#
> thanks,
>
------------------------------------------------------------------------------
_______________________________________________
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-26 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 9:11 [LTP] clock_nanosleep01 TestCase FAIL --> is it known? Jacky Malcles
2009-06-26 11:33 ` Subrata Modak [this message]
2009-07-06 1:37 ` Jiri Palecek
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=1246015998.6196.25.camel@subratamodak.linux.ibm.com \
--to=subrata@linux.vnet.ibm.com \
--cc=Jacky.Malcles@bull.net \
--cc=ltp-list@lists.sourceforge.net \
--cc=maknayak@in.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