Testcase: testRemoveOneAsynchronous took 60.235 sec
FAILED
Waiting for server down
junit.framework.AssertionFailedError: Waiting for server down
at
org.apache.zookeeper.test.QuorumUtil.shutdownAll(QuorumUtil.java:241)
at
org.apache.zookeeper.test.QuorumUtil.startAll(QuorumUtil.java:143)
at
org.apache.zookeeper.test.ReconfigTest.testRemoveOneAsynchronous(ReconfigTest.java:436)
at
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
FAILED
Waiting for server down
junit.framework.AssertionFailedError: Waiting for server down
at
org.apache.zookeeper.test.QuorumUtil.shutdownAll(QuorumUtil.java:241)
at
org.apache.zookeeper.test.QuorumUtil.tearDown(QuorumUtil.java:306)
at
org.apache.zookeeper.test.ReconfigTest.tearDown(ReconfigTest.java:64)
Both of these say they're waiting for server down. The logs are not
particularly helpful. However, this does not fail in the earlier version of
this code for me.
I'm going to abstain from voting on this release, don't think I have the
setup to accommodate even testing the java environment in a way that will
be satisfactory for me given this incongruence. I suspect the problem is
netty-related and not ZK but I don't have the time to keep fussing with
this right now.
C
On Thu, Jul 7, 2016 at 12:01 PM, Flavio P JUNQUEIRA <[email protected]> wrote:
> It has been passing for me and I have a macbook too, but clearly doesn't
> mean there is nothing wrong with the test. You may want to upload logs so
> that we can have a look.
>
> -Flavio
> On 7 Jul 2016 4:40 p.m., "Camille Fournier" <[email protected]> wrote:
>
> > NioNettySuiteTest also regularly fails with this release. Can anyone
> > confirm if this is an env issue?
> >
> > On Thu, Jul 7, 2016 at 11:36 AM, Camille Fournier <[email protected]>
> > wrote:
> >
> > > The NettyNettySuiteTest fails regularly for me in this release and does
> > > not fail in 3.5.1. Is this macbook specific?
> > >
> > > On Thu, Jul 7, 2016 at 11:17 AM, Raúl Gutiérrez Segalés <
> > > [email protected]> wrote:
> > >
> > >> I'll cast my vote today, after I see this behave for a while at a
> > staging
> > >> cluster at work.
> > >>
> > >> Sorry for the lag.
> > >>
> > >> -rgs
> > >> On Jul 7, 2016 12:58 AM, "Flavio P JUNQUEIRA" <[email protected]> wrote:
> > >>
> > >> Hey PMC,
> > >>
> > >> Where are your votes?
> > >>
> > >> -Flavio
> > >> On 7 Jul 2016 5:51 a.m., "Chris Nauroth" <[email protected]>
> > >> wrote:
> > >>
> > >> > I need to leave for vacation now. Unfortunately, the binding votes
> > have
> > >> > not rolled in, so I won't be able to complete the release process
> > >> before I
> > >> > leave. I'll be available again on Monday, 7/18. I can pick up the
> > work
> > >> > then. Alternatively, if the votes comes in during my absence and
> > >> someone
> > >> > else wants to complete the release, please feel free. If we go that
> > >> way,
> > >> > then I could potentially pick up 3.5.3 release manager duties from
> > >> Patrick
> > >> > to make up for it.
> > >> >
> > >> > --Chris Nauroth
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > On 7/6/16, 8:51 AM, "Chris Nauroth" <[email protected]>
> wrote:
> > >> >
> > >> > >With inclusion of my own +1 (non-binding), the current tally on the
> > >> > >[VOTE] for release 3.5.2-alpha candidate 1 is:
> > >> > >
> > >> > >1 +1 (binding)
> > >> > >4 +1 (non-binding)
> > >> > >
> > >> > >Can we please have 2 more PMC members cast a binding vote to push
> > this
> > >> > >[VOTE] to completion? Thank you.
> > >> > >
> > >> > >--Chris Nauroth
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>
