-check from src/c, or ant
test-core-cppunit from the main dir.
On Tue, Aug 3, 2010 at 7:51 PM, Martin Waite waite@gmail.com wrote:
Hi Sergey,
Thanks for the hints.
1) I cannot find any ZK server logs. I have no tmp directory inside
build
directory. This sounds bad.
2) I
Hi Mahadev,
Sorry for the delay in replying: I have been away.
I have rebuilt my debian lenny machine, and started again.
Again, I have the same problem:
~/zookeeper-3.3.1/src/c$ make run-check
make zktest-st zktest-mt
make[1]: Entering directory `/home/martin/zookeeper-3.3.1/src/c'
make[1]:
Hi,
A little more information.
The file TEST-Zookeeper_simpleSystem-st.txt contains some log data:
2010-08-03 13:00:13,550:11391:zoo_i...@zookeeper_init@727: Initiating client
connection, host=127.0.0.1:22181 sessionTimeout=1 watcher=0x8078ed8
sessionId=0 sessionPasswd=null context
I don't really understand how the unit test system is meant to work.
Yes, C tests start ZK server and are tested against it. There are a few that
use mocked server, but that's a legacy code I think.
Re the problem itself:
1) check ZK server logs at build/tmp/ , maybe log contains some info
Yes. It seems you didn't build the server actually.
In the main directory (from where you ran and compile_jute) run ant.
This will invoke ant's default target which will build the server code.
After that run either make run-check from src/c, or ant
test-core-cppunit from the main dir.
On Tue, Aug
Hi,
I am attempting to build the C client on debian lenny.
autoconf, configure, make and make install all appear to work cleanly.
I ran:
autoreconf -if
./configure
make
make install
make run-check
However, the unit tests fail:
$ make run-check
make zktest-st zktest-mt
make[1]: Entering
HI Martin,
Can you check if you have a stale java process (ZooKeeperServer) running
on your machine? That might cause some issues with the tests.
Thanks
mahadev
On 7/14/10 8:03 AM, Martin Waite waite@gmail.com wrote:
Hi,
I am attempting to build the C client on debian lenny.
might be able to avoid some pain by using the
upcoming 3.2.1 release. Once the patches land into that branch your
issues will be resolved w/o you needing to manually apply patches, etc...
I did look at the files you attached - it looks fine so I'm not sure the
issue. The form of this test makes
to 3.2.1 as soon as I
can.
-Todd
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Friday, July 31, 2009 11:38 AM
To: zookeeper-user@hadoop.apache.org; Todd Greenwood
Subject: Re: test failures in branch-3.2
Hi Todd,
Sorry for the clutter/confusion. Usually
: Friday, July 31, 2009 11:38 AM
To: zookeeper-user@hadoop.apache.org; Todd Greenwood
Subject: Re: test failures in branch-3.2
Hi Todd,
Sorry for the clutter/confusion. Usually things aren't this cumbersome
;-)
In particular:
1 committer is on vacation
Mahadev's been out sick for multiple
Hi Todd,
Yes this happens with the branch 3.2. The test-patch link is broken
becasuse of the hadoop split. This file is used for hudson test environment.
It isnt used anywhere else, so the svn co otherwise should be fine. We
should fix it anyways.
Thanks
mahadev
On 7/30/09 2:57 PM, Todd
Thanks Mahadev.
-Original Message-
From: Mahadev Konar [mailto:maha...@yahoo-inc.com]
Sent: Thursday, July 30, 2009 3:00 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: bad svn url : test-patch
Hi Todd,
Yes this happens with the branch 3.2. The test-patch link is broken
becasuse
Todd,
On Jul 30, 2009, at 5:08 PM, Todd Greenwood wrote:
The build succeeds, but not the all of the tests. In previous test
runs,
I noticed an error in org.apache.zookeeper.test.FLETest. It was not
able
to bind to a port or something. Now, after a machine reboot, I'm
getting
different
btw QuorumPeerMainTest uses the CONSOLE appender which is setup in
conf/log4j.properties, now that I think of it perhaps not such a good
idea :-)
If you edited cong/log4j.properties it may be causing the test to fail,
did you do this? (if you run the test by itself using -Dtestcase does
No edits to conf/log4j.properties.
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Thursday, July 30, 2009 9:25 PM
To: Patrick Hunt
Cc: zookeeper-user@hadoop.apache.org
Subject: Re: test failures in branch-3.2
btw QuorumPeerMainTest uses the CONSOLE appender which
: Thursday, July 30, 2009 9:25 PM
To: Patrick Hunt
Cc: zookeeper-user@hadoop.apache.org
Subject: Re: test failures in branch-3.2
btw QuorumPeerMainTest uses the CONSOLE appender which is setup in
conf/log4j.properties, now that I think of it perhaps not such a good
idea :-)
If you edited cong
Patrick, inline.
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Thursday, July 30, 2009 9:13 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: test failures in branch-3.2
Todd Greenwood wrote:
The build succeeds, but not the all of the tests. In previous test
org.apache.zookeeper.server.quorum.QuorumPeerMainTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec
[junit] Test org.apache.zookeeper.server.quorum.QuorumPeerMainTest
FAILED (crashed)
Test Log
Testsuite: org.apache.zookeeper.server.quorum.QuorumPeerMainTest
Tests
needs two patches,
one for each branch) that would be great!
3. Apply ZOOKEEPER-473.patch. Builds, but QuorumPeerMainTest fails (jvm
crashes).
473 is special (unique) in the sense that it changes log4j while the
the vm is running. In general though it's a pretty boring test and
shouldn't
19 matches
Mail list logo
