For more infomation about this bug, visit
Summary: Check concurrent event implementation test
Product: RTT
Version: rtt-trunk
Platform: AMD 64bit
OS/Version: All
Status: NEW
Severity: minor
Priority: P3
Component: Real-Time Toolkit (RTT)
AssignedTo: orocos-dev [..] ...
ReportedBy: peter [dot] soetens [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0
When running the event-test of RTT using the default configuration,
occasionally, there are off-by-one or off-by-two errors when running on
gnulinux.
This test is based on r29804.
For example:
sspr@lt00259:~/src/git/orocos-rtt/build/tests$ ./event-test
.....................
OK (21)
sspr@lt00259:~/src/git/orocos-rtt/build/tests$ ./event-test & ./event-test &
./event-test
[2] 9360
[3] 9362
.....................
OK (21)
............F.........
event_test.cpp:355:Assertion
Test name: EventTest::testConcurrentEmit
equality assertion failed
- Expected: 3454145
- Actual : 3454146
Failures !!!
Run: 21 Failure total: 1 Failures: 1 Errors: 0
[2]- Done ./event-test
sspr@lt00259:~/src/git/orocos-rtt/build/tests$ ............F.........
event_test.cpp:355:Assertion
Test name: EventTest::testConcurrentEmit
equality assertion failed
- Expected: 3000318
- Actual : 3000320
Failures !!!
Run: 21 Failure total: 1 Failures: 1 Errors: 0
[3]+ Exit 1 ./event-test
[Bug 610] Check concurrent event implementation test
For more infomation about this bug, visit
Peter Soetens
<peter [dot] soetens [..] ...> changed:
What |Removed |Added
--------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #3 from Peter Soetens
<peter [dot] soetens [..] ...> 2009-01-13 15:04:57 ---
Fixed on svn trunk/rtt in r29818.
[Bug 610] Check concurrent event implementation test
For more infomation about this bug, visit
--- Comment #2 from Peter Soetens
<peter [dot] soetens [..] ...> 2009-01-13 10:18:18 ---
Created an attachment (id=366)
--> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=366)
mylyn/context/zip
[Bug 610] Check concurrent event implementation test
For more infomation about this bug, visit
--- Comment #1 from Peter Soetens
<peter [dot] soetens [..] ...> 2009-01-13 10:18:17 ---
Created an attachment (id=365)
--> (https://www.fmtc.be/bugzilla/orocos/attachment.cgi?id=365)
Fixes test
The unit test itself was bogus. It did not implement the breakLoop()
function and then did not test if stop() succeeded. Since breakLoop()
returned false, stop() failed, but the unit test assumed the task was
stopped. Hence drawing wrong results.