public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Kang Kai <kai.kang@windriver.com>
To: ltp-list@lists.sourceforge.net
Cc: Zhenfeng.Zhao@windriver.com
Subject: [LTP] [PATCH 3/3] timer_settime/5-3: fix test hung
Date: Thu, 9 Aug 2012 18:30:58 +0800	[thread overview]
Message-ID: <1344508258-25054-4-git-send-email-kai.kang@windriver.com> (raw)
In-Reply-To: <1344508258-25054-1-git-send-email-kai.kang@windriver.com>

This case hangs on sugarbay(intel x86_64) platform.

The root cause is that the case calls timer_settime with time which
already took place and then calls sleep. When the timer expires and
sends signal the sleep will be break.

But on sugarbay the timer always expires before the case enters sleep,
then it always sleeps NUMTESTS * LONGSLEEPTIME seconds. So it exceeds
the time limit set by auto-run test shell script, and reports that it
hangs.

Decrease LONGSLEEPTIME value to avoid this issue.

Signed-off-by: Kang Kai <kai.kang@windriver.com>
---
 .../conformance/interfaces/timer_settime/5-3.c     |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/5-3.c b/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/5-3.c
index 0ad1957..4a47458 100644
--- a/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/5-3.c
+++ b/testcases/open_posix_testsuite/conformance/interfaces/timer_settime/5-3.c
@@ -27,7 +27,7 @@
 
 #define SIGTOTEST SIGALRM
 
-#define LONGSLEEPTIME 10
+#define LONGSLEEPTIME 5
 
 #define NUMTESTS 30
 
@@ -105,4 +105,4 @@ int main(int argc, char *argv[])
 
 	printf("This code should not be executed.\n");
 	return PTS_UNRESOLVED;
-}
\ No newline at end of file
+}
-- 
1.7.5.4


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2012-08-09 10:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 10:30 [LTP] Patches for posix test cases Kang Kai
2012-08-09 10:30 ` [LTP] [PATCH 1/3] pthread_cond_signal/1-1: use sched_yield to sync threads Kang Kai
2012-08-10 10:22   ` Jan Stancek
2012-08-13  2:50     ` Kang Kai
2012-08-23  1:57       ` Wanlong Gao
2012-08-09 10:30 ` [LTP] [PATCH 2/3] mq_open/16-1: use tmp file to share info Kang Kai
2012-08-10  9:31   ` Jan Stancek
2012-09-03  8:45   ` Kang Kai
2012-09-04  6:35     ` Jan Stancek
2012-09-04  9:44       ` Kang Kai
2012-09-04  5:33   ` Wanlong Gao
2012-09-04  7:40     ` Kang Kai
2012-09-04  8:27     ` Kang Kai
2012-09-04  8:41       ` Wanlong Gao
2012-09-04  8:45         ` Kang Kai
2012-08-09 10:30 ` Kang Kai [this message]
2012-08-10  9:16   ` [LTP] [PATCH 3/3] timer_settime/5-3: fix test hung Jan Stancek
2012-08-21  4:01     ` 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=1344508258-25054-4-git-send-email-kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=Zhenfeng.Zhao@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