From: Kang Kai <Kai.Kang@windriver.com>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] mq_timedreceive:5-2: reduce the timeout to be compared
Date: Wed, 11 Apr 2012 16:27:38 +0800 [thread overview]
Message-ID: <4F85407A.9050204@windriver.com> (raw)
In-Reply-To: <4F853592.1010407@cn.fujitsu.com>
On 2012年04月11日 15:41, Wanlong Gao wrote:
> On 04/10/2012 12:02 PM, Wanlong Gao wrote:
>
>> We use (newtime-oldtime) to compare with the TIMEOUT here,
>> but the diff-time we get here is not accurate, the restrict
>> comparing is not reasonable.
>
> Anyone can help reviewing or testing?
Test Yocto Linux 1.2 on arch x86-64 ppc and mips PASS.
Regards,
Kai
>
> Thanks,
> Wanlong Gao
>
>> Signed-off-by: Wanlong Gao<gaowanlong@cn.fujitsu.com>
>> ---
>> .../conformance/interfaces/mq_timedreceive/5-2.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/testcases/open_posix_testsuite/conformance/interfaces/mq_timedreceive/5-2.c b/testcases/open_posix_testsuite/conformance/interfaces/mq_timedreceive/5-2.c
>> index e81d8d5..93421c0 100644
>> --- a/testcases/open_posix_testsuite/conformance/interfaces/mq_timedreceive/5-2.c
>> +++ b/testcases/open_posix_testsuite/conformance/interfaces/mq_timedreceive/5-2.c
>> @@ -32,7 +32,7 @@
>>
>> #define NAMESIZE 50
>> #define BUFFER 40
>> -#define TIMEOUT 3
>> +#define TIMEOUT 2
>>
>> int blocking;
>> void exit_handler(int signo)
>> @@ -70,7 +70,7 @@ int main()
>> sigemptyset(&act.sa_mask);
>> sigaction(SIGABRT,&act, 0);
>>
>> - ts.tv_sec = time(NULL) + TIMEOUT;
>> + ts.tv_sec = time(NULL) + TIMEOUT + 1;
>> ts.tv_nsec = 0;
>> oldtime = time(NULL);
>> mq_timedreceive(mqdes, msgrv, BUFFER, NULL,&ts);
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next parent reply other threads:[~2012-04-11 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334030557-24170-1-git-send-email-gaowanlong@cn.fujitsu.com>
[not found] ` <4F853592.1010407@cn.fujitsu.com>
2012-04-11 8:27 ` Kang Kai [this message]
2012-04-11 8:34 ` [LTP] [PATCH] mq_timedreceive:5-2: reduce the timeout to be compared Wanlong Gao
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=4F85407A.9050204@windriver.com \
--to=kai.kang@windriver.com \
--cc=ltp-list@lists.sourceforge.net \
/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