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

Posted to commits@distributedlog.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2017/01/05 06:57:58 UTC

[jira] [Resolved] (DL-167) Fix flaky TestLeastLoadPlacementPolicy#testCalculateUnequalWeight

     [ https://issues.apache.org/jira/browse/DL-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo resolved DL-167.
--------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.0

Merged the pull request. [~xieliang007] thank you so much!

> Fix flaky TestLeastLoadPlacementPolicy#testCalculateUnequalWeight
> -----------------------------------------------------------------
>
>                 Key: DL-167
>                 URL: https://issues.apache.org/jira/browse/DL-167
>             Project: DistributedLog
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 0.4.0
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>             Fix For: 0.4.0
>
>
> From https://builds.apache.org/job/distributedlog-precommit-pullrequest/63/com.twitter$distributedlog-service/testReport/com.twitter.distributedlog.service.placement/TestLeastLoadPlacementPolicy/testCalculateUnequalWeight/ , we can see numStreams = 1, therefore highestLoadSeen - lowestLoadSeen should be equals to maxLoad.get()



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)