[jira] [Commented] (CURATOR-411) Make Tests Great Again

2017-05-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005848#comment-16005848 ] ASF GitHub Bot commented on CURATOR-411: Github user zarfide commented on the issue:

[GitHub] curator issue #221: [CURATOR-411] Fix various testing issues

2017-05-10 Thread zarfide
Github user zarfide commented on the issue: https://github.com/apache/curator/pull/221 I was able to get two full clean test runs in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

Build failed in Jenkins: Curator #1036

2017-05-10 Thread Apache Jenkins Server
See Changes: [randgalt] In testNewMembers, make sure client connects to one of the nodes in the -- [...truncated 1.26 MB...] Results : Tests run: 0, Failures: 0, Errors: 0,

Jenkins build is still unstable: Curator » Curator Framework #1036

2017-05-10 Thread Apache Jenkins Server
See

Build failed in Jenkins: Curator » Curator Async #1036

2017-05-10 Thread Apache Jenkins Server
See -- [INFO] [INFO]

[jira] [Commented] (CURATOR-411) Make Tests Great Again

2017-05-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16005697#comment-16005697 ] ASF GitHub Bot commented on CURATOR-411: Github user cammckenzie commented on the issue:

[GitHub] curator issue #221: [CURATOR-411] Fix various testing issues

2017-05-10 Thread cammckenzie
Github user cammckenzie commented on the issue: https://github.com/apache/curator/pull/221 The reconfiguration case seems to be better now. I'm still seeing failures on the TestFailedDeleteManager.testLostSession It seems that at line 77, it is sometimes getting an

Build failed in Jenkins: Curator #1035

2017-05-10 Thread Apache Jenkins Server
See Changes: [randgalt] don't clear quorumPeer as it might cause an NPE [randgalt] Only change from 5 to 4 to avoid flaky test [randgalt] KeeperException.SessionExpiredException is also valid for

Build failed in Jenkins: Curator » Curator Async #1035

2017-05-10 Thread Apache Jenkins Server
See -- [INFO] [INFO]

Jenkins build became unstable: Curator » Curator Framework #1035

2017-05-10 Thread Apache Jenkins Server
See

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

2017-05-10 Thread Apache Jenkins Server
See

[jira] [Commented] (CURATOR-411) Make Tests Great Again

2017-05-10 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/CURATOR-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16004518#comment-16004518 ] ASF GitHub Bot commented on CURATOR-411: Github user Randgalt commented on the issue:

[GitHub] curator issue #221: [CURATOR-411] Fix various testing issues

2017-05-10 Thread Randgalt
Github user Randgalt commented on the issue: https://github.com/apache/curator/pull/221 @cammckenzie @zarfide please re-rest. I made the following changes: - testNewMembers() only tries to go from 5 to 4. I'm guessing the flakiness is going from 5 to 3 -