The problem is related to T8033. The fix for this bug can fail under rare circumstances.
In line 128 and 129 of mitkVirtualTrackingDeviceTest the position and the modified time are got from a tool:
tracker->GetToolByName("while Running")->GetPosition(posAfter0);
unsigned long tmpAfterMTime = tracker->GetToolByName("while Running")->GetMTime();
The position of the tool can be changed directly after getting the position. In this case the modified time is already changed when calling GetMTime().
[cfea35]: Merge branch 'bug-17791-virtual-tracking-device-test-fails-randomly'
2014-05-13 15:51:07 Adrian Winterstein [bf012d]
COMP: Deactivated the test as it seems to be a concurrency problem.
User wintersa has pushed new remote branch:
bug-17791-virtual-tracking-device-test-fails-randomly
This bug could not be fixed during the 2015.05 release.
Setting target_milestone to AfterNextRelease
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs