apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject watch out for thread_cond_timedwait problems
Date Tue, 02 Jul 2002 13:39:31 GMT
I dunno what the cause is yet, but I'm getting testlock failures for
the last day or so.

Tru64:

Run of ./testlock -f /tmp/rasub failed, exit status is 63488.
stdout:
APR Locks Test
==============

thread_mutex test
    Initializing the mutex                                  OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_rwlock Tests
    Initializing the apr_thread_rwlock_t                    OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_cond Tests
    Initializing the first apr_thread_mutex_t               OK
    Initializing the second apr_thread_mutex_t              OK
    Initializing the apr_thread_cond_t                      OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_cond_timedwait Tests
    Initializing the first apr_thread_mutex_t               OK
    Initializing the apr_thread_cond_t                      OK
    Waiting for condition for 5 seconds                     Failed! (bad timer)
stderr:
thread_cond_timedwait test failed : [22] Invalid argument

AIX:

Run of ./testlock  failed, exit status is 63488.
stdout:
APR Locks Test
==============

thread_mutex test
Initializing the mutex                                  OK
Starting all the threads                                OK
Waiting for threads to exit                             OK
Test passed
thread_rwlock Tests
Initializing the apr_thread_rwlock_t                    OK
Starting all the threads                                OK
Waiting for threads to exit                             OK
Test passed
thread_cond Tests
Initializing the first apr_thread_mutex_t               OK
Initializing the second apr_thread_mutex_t              OK
Initializing the apr_thread_cond_t                      OK
Starting all the threads                                OK
Waiting for threads to exit                             OK
Test passed
thread_cond_timedwait Tests
Initializing the first apr_thread_mutex_t               OK
Initializing the apr_thread_cond_t                      OK
Waiting for condition for 5 seconds                     Failed! (bad
timer)
stderr:
thread_cond_timedwait test failed : [22] A system call received a
parameter that is not valid.


Linux:

Run of ./testlock  failed, exit status is 63488.
stdout:
APR Locks Test
==============

thread_mutex test
    Initializing the mutex                                  OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_rwlock Tests
    Initializing the apr_thread_rwlock_t                    OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_cond Tests
    Initializing the first apr_thread_mutex_t               OK
    Initializing the second apr_thread_mutex_t              OK
    Initializing the apr_thread_cond_t                      OK
    Starting all the threads                                OK
    Waiting for threads to exit                             OK
Test passed
thread_cond_timedwait Tests
    Initializing the first apr_thread_mutex_t               OK
    Initializing the apr_thread_cond_t                      OK
    Waiting for condition for 5 seconds                     Failed (late TIMEUP)!
    The timer returned in 5292029 usec!
stderr:
thread_cond_timedwait test failed : [20507] The timeout specified has expired

-- 
Jeff Trawick | trawick@attglobal.net
Born in Roswell... married an alien...

Mime
View raw message