You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@helix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/11/02 21:29:00 UTC

[jira] [Commented] (HELIX-786) TEST: Make TestQuotaBasedScheduling stable

    [ https://issues.apache.org/jira/browse/HELIX-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673702#comment-16673702 ] 

Hudson commented on HELIX-786:
------------------------------

FAILURE: Integrated in Jenkins build helix #1570 (See [https://builds.apache.org/job/helix/1570/])
[HELIX-786] TEST: Make TestQuotaBasedScheduling stable (narendly: rev bced0996ed65c9a886b5e04788e2cc1c88fc37b1)
* (edit) helix-core/src/test/java/org/apache/helix/integration/task/TestQuotaBasedScheduling.java
[HELIX-786] TASK: Fix stuck tasks after Participant connection loss (narendly: rev dc25bac1ebdcddb08aaab2765abfe72008b06a31)
* (edit) helix-core/src/main/java/org/apache/helix/task/AbstractTaskDispatcher.java


> TEST: Make TestQuotaBasedScheduling stable
> ------------------------------------------
>
>                 Key: HELIX-786
>                 URL: https://issues.apache.org/jira/browse/HELIX-786
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Hunter L
>            Assignee: Hunter L
>            Priority: Major
>
> Because recent changes caused the Controller to run slower, TestQuotaBasedScheduling was being unstable. This RB fixes this.
> Changelist:
> 1. Use polling instead of Thread.sleep()



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