You're right, there is no "stat" usage in this test.
I suspect I know what this is. I just looked at that CI host and it
has 2 slots. I bet that some other test (either another ZK or hbase or
flume) may have run on that same host/port at the same time my test
was running. That would account for th
Btw, from the stack traces all of the servers seem to be in a healthy
state, complete through leader election and following properly.
>From my phone
On Nov 8, 2011 2:01 PM, "Camille Fournier" wrote:
> Anyone know why Patrick's log file might be showing a lot of this
> before the error?
>
> 2011-
Anyone know why Patrick's log file might be showing a lot of this
before the error?
2011-11-06 01:02:39,905 [myid:2] - INFO
[Thread-76:NIOServerCnxn$StatCommand@655] - Stat command output
This test never does a stat call, it uses a ZK client to connect in.
This seems strange, perhaps the issue is
I'm currently trying to wrap up ZOOKEEPER-1292, and I can move to
early abandonment once I'm done here.
-Flavio
On Nov 8, 2011, at 1:20 AM, Camille Fournier wrote:
Sorry you're feeling bad, Patrick! We can take it from here.
I would really like to get some clarification on this test from so
Sorry you're feeling bad, Patrick! We can take it from here.
I would really like to get some clarification on this test from some
of the LE experts. What does it really mean that this test is failing?
Is this sort of failure that means that sometimes we have server
startup that takes a bit longer
That's fine (direction re 1-4). However my CI branch 3.4 build failed
over the w/e (once out of four runs). This is AFTER "Preparing for
release 3.4.0 - take 2" was applied (so testing includes 1270, 1264,
etc...)
Notice testEarlyLeaderAbandonment is failing. I have attached the log
file to ZOOKEE
I'm fine with your proposal. -Flavio
On Nov 5, 2011, at 8:15 PM, Camille Fournier wrote:
2 has been flaky for so long, not sure whether it's worth being a
blocker.
The AsyncHammerTests never pass for me locally. Not sure if it's a
problem or not... I am tempted to go with Mahadev on this and
2 has been flaky for so long, not sure whether it's worth being a blocker.
The AsyncHammerTests never pass for me locally. Not sure if it's a
problem or not... I am tempted to go with Mahadev on this and get this
3.4 release out the door. I would be happy to help manage a 3.4.1
release soon thereaf
If 2) is flakey, we need to fix it, no?
-Flavio
On Nov 5, 2011, at 6:14 PM, Patrick Hunt wrote:
I ran the 1270-1194 patch continually overnight (trunk) in my ci env,
after ~25 test runs I saw 4 failures:
1) #402 - QuorumTest.testFollowersStartAfterLeader
2) #407 - org.apache.zookeeper.test.F
Thanks for stats Pat. 3) and 4) though a little worrisome but we can
open a jira against 3.4.1 and look at fixing them later. I'd think
they shouldnt be a blocker for 3.4 release. What do others think?
thanks
mahadev
On Sat, Nov 5, 2011 at 10:14 AM, Patrick Hunt wrote:
> I ran the 1270-1194 pat
I ran the 1270-1194 patch continually overnight (trunk) in my ci env,
after ~25 test runs I saw 4 failures:
1) #402 - QuorumTest.testFollowersStartAfterLeader
2) #407 - org.apache.zookeeper.test.FLETest.testLE
3) #410 - org.apache.zookeeper.test.AsyncHammerTest.testHammer
4) #415 - org.apache.zook
11 matches
Mail list logo
