From c54e6f5e56a9c26740099712ddccc794643fbad2 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 14 Oct 2009 21:34:43 +0000 Subject: 2009-10-14 Joel Sherrill * psxtimer01/psxtimer.c: It is not necessarily an error for the time remaining to not equal the period. --- testsuites/psxtests/ChangeLog | 5 +++++ testsuites/psxtests/psxtimer01/psxtimer.c | 14 +++++++++++++- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/testsuites/psxtests/ChangeLog b/testsuites/psxtests/ChangeLog index cab66b1aca..d983e1d605 100644 --- a/testsuites/psxtests/ChangeLog +++ b/testsuites/psxtests/ChangeLog @@ -1,3 +1,8 @@ +2009-10-14 Joel Sherrill + + * psxtimer01/psxtimer.c: It is not necessarily an error for the time + remaining to not equal the period. + 2009-10-11 Joel Sherrill * psx05/init.c, psx05/psx05.scn: Add test for bad mutex type. diff --git a/testsuites/psxtests/psxtimer01/psxtimer.c b/testsuites/psxtests/psxtimer01/psxtimer.c index 52d3b4d0cc..9aee241a20 100644 --- a/testsuites/psxtests/psxtimer01/psxtimer.c +++ b/testsuites/psxtests/psxtimer01/psxtimer.c @@ -201,10 +201,22 @@ void * task_b (void *arg) perror ("Error in timer_gettime\n"); rtems_test_exit(0); } + +#if 0 + /* + * It is not an error if they are not equal. A clock tick could occur + * and thus they are close but not equal. Can we test for this? + */ if ( !_Timespec_Equal_to( &timerdata.it_value, &my_period) ){ - perror ("Error in Task B timer_gettime\n"); + printf( "NOT EQUAL %d:%d != %d:%d\n", + timerdata.it_value.tv_sec, + timerdata.it_value.tv_nsec, + my_period.tv_sec, + my_period.tv_nsec + ); rtems_test_exit(0); } +#endif pthread_mutex_lock (&data.mutex); clock = time(NULL); -- cgit v1.2.3