Looks like some diff in the errno reported in 10.4 (I'm on karmic and it
const string INVALID_HOST("host1:1111+host:123");
22 is EINVAL
So this is fine for 3.3.1, but enter a JIRA to address it in the next
On 05/13/2010 08:19 AM, Andrei Savu wrote:
All the Junit tests work as expected but I've got a failing test on
the C client. I have attached the log messages.
Is this an expected (accepted) error? I'm now running the tests on
I'm testing on: Ubuntu 10.4 LTS Server Edition (64 bit) running inside
VMWare Workstation on Windows7
$ java -version
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
$ gcc -v
Using built-in specs.
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
--enable-shared --enable-multiarch --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--program-suffix=-4.4 --enable-nls --enable-clocale=gnu
--enable-libstdcxx-debug --enable-plugin --enable-objc-gc
--disable-werror --with-arch-32=i486 --with-tune=generic
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
On Wed, May 12, 2010 at 10:01 PM, Flavio Junqueira<f...@yahoo-inc.com> wrote:
+1, works for me as well.
On May 12, 2010, at 7:58 PM, Benjamin Reed wrote:
+1, things check out for me too.
On 05/11/2010 11:19 PM, Henry Robinson wrote:
+1, Java tests pass for me, as do Python ones.
On 11 May 2010 22:32, Patrick Hunt<ph...@apache.org> wrote:
+1, tests pass for me, also verified that nc/zktop worked properly on a
real cluster (4letter word fix).
On 05/07/2010 11:25 AM, Patrick Hunt wrote:
I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix
release addressing seventeen issues (one critical) -- see the release
notes for details.
*** Please download, test and VOTE before the
*** vote closes 11am pacific time, Wednesday, May 12.***
Should we release this?