curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails
Date Fri, 21 Aug 2015 18:22:46 GMT

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

Jordan Zimmerman commented on CURATOR-231:
------------------------------------------

There's a simple fix for this but I'm concerned that it will alter the implied contract. Currently,
when an item is re-queued it goes to the end of the queue. The simple fix is to recreate it
in place. I wonder if we need to maintain the undocumented by implicit contract?

> TestDistributedQueue.testRetryAfterFailure_Curator56 fails
> ----------------------------------------------------------
>
>                 Key: CURATOR-231
>                 URL: https://issues.apache.org/jira/browse/CURATOR-231
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Recipes, Tests
>            Reporter: Mike Drob
>            Priority: Blocker
>             Fix For: 2.9.0
>
>
> Per Jenkins: https://builds.apache.org/job/Curator/lastBuild/org.apache.curator$curator-recipes/testReport/org.apache.curator.framework.recipes.queue/TestDistributedQueue/testRetryAfterFailure_Curator56/



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

Mime
View raw message