Troubleshooting the Kernel Scheduler Test (Windows Embedded CE 6.0)
1/6/2010
Test case 65537 may fail if the constants for the variable tick scheduler are improperly defined. This can happen if the tick goes backward, is negatively defined, or is not in synch with Sleep or OEMRealTime. If this test case fails, disregard the results of test case 65538.
A failure in test case 65538 means the threads are awakening too soon or too late (in the case of the highest priority thread). Refer to the documentation for the variable tick scheduler to assure that it is implemented correctly.
For more troubleshooting help, see Troubleshooting the CETK Tests.