... which became apparent after switching to the new Thread-wrapper implementation ... the reason is a bug in the Thread-Monitor (which will also be reworked soon)
49 lines
829 B
Text
49 lines
829 B
Text
TESTING "Library Test Suite: concurrency helpers" ./test-suite --group=common
|
|
|
|
|
|
|
|
TEST "Multithread Locking by Monitor" SyncLocking_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Multithread Locking class level" SyncClasslock_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "N-fold synchronisation barrier" SyncBarrier_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Yield-waiting sync performance" SyncBarrierPerformance_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Wait/Notify on Object Monitor" SyncWaiting_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Wait/Notify with timeout" SyncTimedwait_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Create 20 Threads passing context" ThreadWrapper_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Waiting on Thread termination" ThreadWrapperJoin_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|
|
TEST "Detect code runing in a given Thread" ThreadWrapperSelfRecognitionTest_test <<END
|
|
return: 0
|
|
END
|
|
|
|
|