[
https://issues.apache.org/jira/browse/HELIX-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547170#comment-16547170
]
Hudson commented on HELIX-736:
------------------------------
FAILURE: Integrated in Jenkins build helix #1515 (See
[https://builds.apache.org/job/helix/1515/])
[HELIX-736] Modify TestGetLastScheduledTaskTimestamp for increased (narendly:
rev 047ad51e8b243dbbd268aa9ba954623949eba27d)
* (edit)
helix-core/src/test/java/org/apache/helix/task/TestGetLastScheduledTaskTimestamp.java
> 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
> Priority: Major
>
> 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)
