The failure in timer_getoverrun
Xiong, Crystal
crystal.xiong at intel.com
Fri Feb 20 00:54:26 UTC 2004
Hi all,
I ran a test case for timer_getoverrun in posixtestsuite project based on kernel 2.6.1 with libc-2004-02-01. The case didn't return the expected overrun numbers as expected.
Platform:
--------------------
libc: 2004-02-01
Linux kernel: 2.6.1-mm2 SMP on ia32
gcc-3.3.3-20040209
Redhat EL-3.0-update1
Test Case and Output
----------------------
The case can be found at http://cvs.sourceforge.net/viewcvs.py/posixtest/posixtestsuite/conformance/interfaces/timer_getoverrun/2-2.c
Output: FAIL: 62 overruns sent; expected 75
I know there maybe some problems to let nanosleep sleep for the time equal to the time of the expired times. But is there any way to make sure the timer expire the accurate times we want? So then we can get the correct overrun numbers?
Attached the strace log.
Thanks,
Crystal
--------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: strace.log
Type: application/octet-stream
Size: 5157 bytes
Desc: strace.log
URL: <http://listman.redhat.com/archives/phil-list/attachments/20040220/e1d782b2/attachment.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT272527.txt
URL: <http://listman.redhat.com/archives/phil-list/attachments/20040220/e1d782b2/attachment.txt>
More information about the Phil-list
mailing list