The threads.0 test runs two threads, one named "fast" with a 100 us period and one named "slow" with a 1 ms period. The fast thread has a sampler component that samples threadtest.counter, which increases by one each run of the thread. The slow thread resets the counter so it goes back to 1 again.
The current test verifies that the fast thread runs exactly ten times between each run of the slow one. This works well on actual hardware, but doesnt work on my KVM virtual machines. The scheduling is way off. But it's not a bug in EMC2 or RTAI, it's just how RTAI works on this laggy "hardware". Jeff said the same at 21:01:59 here: <http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-11-10.txt> I propose we relax the test to verify only that both threads get run at all, by verifying that the sampler in the fast thread records a sequence of integers that starts at 1 and increases by one each time, or else gets reset back to 1. It's a simple thing to test and I have it working in my sandbox. Do you folks who actually know this stuff agree that this is the way to go? -- Sebastian Kuzminsky how many no money boys are crazy how many boys are raw how many no money boys are rowdy how many start a war ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
