Ill check into the Curator logging aspect and report back. Thanks for the feedback on this guys!
On Jan 11, 2018 7:23 AM, "Keith Turner" <ke...@deenlo.com> wrote: > Some of these error messages are caused by testing Oracle failures. > For those test that are testing failures we could manually set the log > level to fatal by calling the log4j api. After the test we could > revert the setting in a finally block. > > Some of the error messages are from Curator. We need to determine if > Curator is erroneously logging or if Fluo us using it incorrectly. In > the past we fixed some logging issue in Curator. > > On Wed, Jan 10, 2018 at 5:46 PM, Kenneth Mcfarland > <kennethmcfarl...@apache.org> wrote: > > I've been running mvn verify and see errors for some integration tests > such > > as OracleIT and TimestampTrackerIT > > > > I've done this a few times with fairly deterministic results. There is an > > open issue but the log messages and tests/stack traces are different. > > > > Just checking to see if anyone else can reproduce this. I'm on 16.04 x64 > > Ubuntu building from master. > > > > Thank you! >
