Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
MIME-Version: 1.0
Date: Wed, 25 May 2016 13:31:52 +1000
Message-ID: <CANykduZ_8vgz5wp19_am_G7s-CFk7_gN-D0z2Dt1NdxQ5Pjs+g@mail.gmail.com>
Subject: CURATOR-3.0 tests
From: Cameron McKenzie <mckenzie.cam@gmail.com>
To: "dev@curator.apache.org" <dev@curator.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c1249c6833d630533a25038
archived-at: Wed, 25 May 2016 03:31:57 -0000

--94eb2c1249c6833d630533a25038
Content-Type: text/plain; charset=UTF-8

Guys,
There's a test TestFrameworkBackground:testErrorListener that is failing
consistently on the CURATOR-3.0 branch.

I can't see how it has ever worked. It seems to try and provoke an error
via a bad ACL provider.

But this ACL provider is called by the CreateBuilderImpl prior to the
backgrounding call, which means that the exception that it throws happens
in the main Thread of the unit test. So, it just throws an
UnsupportedOperationException which is propogated up the stack at which
point the unit test fails.

So, I will look at fixing this, but I just don't understand how it ever
worked?
cheers

--94eb2c1249c6833d630533a25038--