Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
This test was experiencing an intermittent failure. No inherent faults of its own, but sometimes tasks were not being given enough resource/time to be scheduled and register the timestamp, which is expected depending on how fast the system is running. One area of improvement was that TestGetLastScheduledTaskTimestamp was using a long value 0 for invalid or unscheduled timestamps. It will use -1L from now on, which is the invalid flag TaskDriver uses.
Changlist:
1. Change the flag for invalid or unscheduled timestamps from 0 to -1L in TestGetLastScheduledTaskTimestamp