Hunter L created HELIX-736:
------------------------------

             Summary: Modify TestGetLastScheduledTaskTimestamp for increased 
stability
                 Key: HELIX-736
                 URL: https://issues.apache.org/jira/browse/HELIX-736
             Project: Apache Helix
          Issue Type: Improvement
            Reporter: Hunter L


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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to