I'm guessing it's something to do with your local system. You had previously filed KUDU-2770 regarding incompatibilities with newer versions of glibc; what system/distro are you running on? Are you using _any_ Kudu patches whatsoever, even just to get the build (or thirdparty build) working?
FWIW, these tests pass locally for me (running against master) and they're passing in Kudu precommit tests regularly. Could you try to run the C++ test suite? They're easier to debug when they fail. On Tue, Apr 16, 2019 at 12:53 AM Clemens Valiente <clemens.valie...@trivago.com> wrote: > > Hi, > > > I added these flags after the initial runs that complained about > rpc_max_message_size exceeded in the tests. That got me one step further to > the connection failed error. > > > I tried running the tests both on master and on the kudu 1.9.0 release (with > the appropriate kudu build), with and without my patch. > > ________________________________ > From: Adar Lieber-Dembo <a...@cloudera.com.INVALID> > Sent: 14 April 2019 19:59:45 > To: dev@kudu.apache.org > Subject: Re: java unit tests failing when starting MiniKuduCluster > > It might be related to your local changes. This caught my eye: > > extra_master_flags: "--rpc_max_message_size=3860733440" > extra_tserver_flags: "--rpc_max_message_size=3860733440" > > Why did you have to add this configuration? What happens if you remove > it? On a related note, do the tests still fail if you rebuild from a > clean working tree (i.e. without your patches)? > > On Sat, Apr 13, 2019 at 12:52 PM Clemens Valiente > <clemens.valie...@trivago.com> wrote: > > > > Hi, > > > > I have a few fixes for the kudu-mapreduce package and wanted to add unit > > tests but neither the existing nor the newly added unit tests can be run on > > my system. > > > > I managed to build kudu and theMiniKuduCluster starts up but then fails > > with connection/timeout issues. > > > > I think this might point at the problem: > > > > 16:42:05.780 [INFO - cluster stderr printer] (MiniKuduCluster.java:543) > > 0410 16:42:05.779084 (+3053866us) negotiation.cc:304] Negotiation complete: > > Timed out: Server connection negotiation failed: server connection from > > 127.0.0.1:60698 > > > > Though I have no explanation as to why kudu would not be able to make local > > connections within my machine. (fedora 29, OpenSSL 1.1.1b FIPS 26 Feb 2019) > > I attached the full test report. Can someone help me figure out how to > > further debug this, or is there any additional information I can provide? > > > > Best Regards > > Clemens Valiente
