[jira] [Updated] (CURATOR-242) TestDistributedQueue.testCustomExecutor() is failing

[ https://issues.apache.org/jira/browse/CURATOR-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-242: -- Component/s: Recipes > TestDistributedQueue.testCustomExecutor() is failing > -

[jira] [Updated] (CURATOR-252) TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed

[ https://issues.apache.org/jira/browse/CURATOR-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-252: -- Affects Version/s: (was: 2.9.0) Priority: Blocker (was: Major) Fix Version/s:

[jira] [Created] (CURATOR-252) TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed

Mike Drob created CURATOR-252: - Summary: TestLeaderSelectorEdges::createProtectedNodeInBackgroundTest failed Key: CURATOR-252 URL: https://issues.apache.org/jira/browse/CURATOR-252 Project: Apache Curator

[jira] [Updated] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-243: -- Component/s: Recipes > TestDistributedIdQueue.testRequeuingWithLock is failing > --

[jira] [Updated] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-243: -- Labels: jenkins (was: ) > TestDistributedIdQueue.testRequeuingWithLock is failing > --

[jira] [Updated] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated CURATOR-231: -- Labels: jenkins (was: ) > TestDistributedQueue.testRetryAfterFailure_Curator56 fails > ---

[jira] [Created] (CURATOR-251) TestResetConnectionWithBackgroundFailure::testConnectionStateListener failing

Mike Drob created CURATOR-251: - Summary: TestResetConnectionWithBackgroundFailure::testConnectionStateListener failing Key: CURATOR-251 URL: https://issues.apache.org/jira/browse/CURATOR-251 Project: Apac

Jenkins build is unstable: Curator-3.0 #1

See

Jenkins build is unstable: Curator-3.0 » Curator Recipes #1

See

Re: Next Steps

https://builds.apache.org/job/Curator-3.0/ On Fri, Aug 21, 2015 at 12:54 PM, Jordan Zimmerman < jor...@jordanzimmerman.com> wrote: > Good idea. You should have perms to create it. If not, let me know. > > > > On August 21, 2015 at 12:53:39 PM, Mike Drob (md...@apache.org) wrote: > > Is there a cu

[jira] [Commented] (CURATOR-247) Extend Curator's connection state to support SESSION_LOST

[ https://issues.apache.org/jira/browse/CURATOR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707620#comment-14707620 ] Jordan Zimmerman commented on CURATOR-247: -- Implementation notes so far: * It ma

[jira] [Issue Comment Deleted] (CURATOR-246) Parent task for adding a SESSION_LOST connection state, etc.

[ https://issues.apache.org/jira/browse/CURATOR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman updated CURATOR-246: - Comment: was deleted (was: Implementation notes so far: * It makes more sense to alter t

[jira] [Commented] (CURATOR-246) Parent task for adding a SESSION_LOST connection state, etc.

[ https://issues.apache.org/jira/browse/CURATOR-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707619#comment-14707619 ] Jordan Zimmerman commented on CURATOR-246: -- Implementation notes so far: * It m

Jenkins build is back to stable : Curator #944

See

Jenkins build is back to stable : Curator » Curator Recipes #944

See

[jira] [Commented] (CURATOR-233) Bug in double barrier

[ https://issues.apache.org/jira/browse/CURATOR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707361#comment-14707361 ] Mike Drob commented on CURATOR-233: --- Hi J D! Thanks for attaching your test case, I wil

[jira] [Resolved] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-231. -- Resolution: Fixed I ended up fixing so that it maintains the old implied contract. Not

[jira] [Commented] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ 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'

[jira] [Comment Edited] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707207#comment-14707207 ] Jordan Zimmerman edited comment on CURATOR-231 at 8/21/15 6:22 PM:

[jira] [Comment Edited] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707195#comment-14707195 ] Jordan Zimmerman edited comment on CURATOR-231 at 8/21/15 6:19 PM:

[jira] [Commented] (CURATOR-231) TestDistributedQueue.testRetryAfterFailure_Curator56 fails

[ https://issues.apache.org/jira/browse/CURATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707195#comment-14707195 ] Jordan Zimmerman commented on CURATOR-231: -- This was introduced by CURATOR-224

[jira] [Resolved] (CURATOR-250) CURATOR-224 caused regression of CURATOR-56

[ https://issues.apache.org/jira/browse/CURATOR-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob resolved CURATOR-250. --- Resolution: Duplicate Dup of CURATOR-231? > CURATOR-224 caused regression of CURATOR-56 > --

[jira] [Created] (CURATOR-250) CURATOR-224 caused regression of CURATOR-56

Jordan Zimmerman created CURATOR-250: Summary: CURATOR-224 caused regression of CURATOR-56 Key: CURATOR-250 URL: https://issues.apache.org/jira/browse/CURATOR-250 Project: Apache Curator

Re: Next Steps

Good idea. You should have perms to create it. If not, let me know. On August 21, 2015 at 12:53:39 PM, Mike Drob (md...@apache.org) wrote: Is there a curator-3.0 jenkins job? On Wed, Aug 19, 2015 at 4:47 PM, Cameron McKenzie wrote: > Nope, all sorted. > Thanks. > > On Thu, Aug 20

[jira] [Commented] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707142#comment-14707142 ] Jordan Zimmerman commented on CURATOR-243: -- done - I did it as "merge master". T

Re: Next Steps

Is there a curator-3.0 jenkins job? On Wed, Aug 19, 2015 at 4:47 PM, Cameron McKenzie wrote: > Nope, all sorted. > Thanks. > > On Thu, Aug 20, 2015 at 6:29 AM, Jordan Zimmerman < > jor...@jordanzimmerman.com> wrote: > > > Resending - is there something I need to do on watchers? > > > > -Jordan >

[jira] [Commented] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707133#comment-14707133 ] Mike Drob commented on CURATOR-243: --- Does this need to be merged into 3.0? > TestDistr

[jira] [Resolved] (CURATOR-243) TestDistributedIdQueue.testRequeuingWithLock is failing

[ https://issues.apache.org/jira/browse/CURATOR-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jordan Zimmerman resolved CURATOR-243. -- Resolution: Fixed The test was too timing-dependent. Most of the time, the code would b

[jira] [Commented] (CURATOR-249) Update all Curator recipes to use new pluggable Error Handler

[ https://issues.apache.org/jira/browse/CURATOR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706754#comment-14706754 ] Mike Drob commented on CURATOR-249: --- I can do this once the error handlers are done. >