looks like you didn't run the first step in the parent directory ? ant jar compile-test
The patch is not relevant for 3.4.6, the systest should run without it, although the first steps are the same. Take a look at src/java/systest/README.txt On Mon, Nov 10, 2014 at 9:40 PM, Ibrahim <i.s.el-san...@newcastle.ac.uk> wrote: > Hi Alexander > > * Thank you for sending the link. I am starting running it. This test uses > the zookeeper-trunk. Because I am using zookeeper 3.4.6. But there is an > error when I run step 2 "Go to zookeeper-trunk\src\contrib\fatjar, run "ant > jar"? > > [echo] contrib: fatjar > init-contrib: > compile: > [echo] contrib: fatjar > [javac] > D:\workspacez\zookeeperallversions\trunk\src\contrib\build-contrib.xml:125: > warning: 'includeantruntime' was not set, defaulting to > build.sysclasspath=last; set to false for repeatable builds > jar: > [echo] contrib: fatjar > > BUILD FAILED > D:\workspacez\zookeeperallversions\trunk\src\contrib\fatjar\build.xml:31: > D:\workspacez\zookeeperallversions\trunk\build\test\classes does not exist. > > Total time: 380 milliseconds > > > so is it possible to apply the test (ZOOKEEPER-2023) in 3.4.6? i > > * "if I remember correctly the way it measures latency is by writing down > the invocation time in the context object given to an async command. Then > when the callback is invoked you get the context object back and can > calculate the latency." > > Yes, you are right. Also I manage to collect the latency result by plug-in > some line code in Zookeeper classes (FinalRequestProcessor.java and > ServerStats.java). > > > Thank a lot Alexander > > Ibrahim > > > > > -- > View this message in context: > http://zookeeper-user.578899.n2.nabble.com/Best-strategy-to-test-Zookeeper-tp7580580p7580586.html > Sent from the zookeeper-user mailing list archive at Nabble.com. >
