* Maxime Petazzoni <[email protected]> [2012-03-28 15:24:03]:
> * Alejandro Abdelnur <[email protected]> [2012-03-28 20:51:54]: > > > Nah, that will pull hadoop-auth to the client and server side from 0.23.1, > > which does not depend on any of hadoop (by design of the author ;D ) > > Ok. It does build when I put back the dependency on hadoop-auth 0.23.1 > for the Oozie client, but I'm not sure this is the right thing because > the full project builds, while it should have failed on > HadoopAccessorService because of the different API in > org.apache.hadoop.security.UserGroupInformation (I did not replace that > file yet). > > So, why is the build not failing? Also, after the compilation succeeds, > the following test fails: > > testBundleStatusTransitServiceSucceeded3(org.apache.oozie.service.TestStatusTransitService) > Time elapsed: 14.692 sec <<< FAILURE! > junit.framework.AssertionFailedError: expected:<SUCCEEDED> but was:<RUNNING> > at junit.framework.Assert.fail(Assert.java:47) > at junit.framework.Assert.failNotEquals(Assert.java:282) > at junit.framework.Assert.assertEquals(Assert.java:64) > at junit.framework.Assert.assertEquals(Assert.java:71) > at > org.apache.oozie.service.TestStatusTransitService.testBundleStatusTransitServiceSucceeded3(TestStatusTransitService.java:592) > > But I'm not sure why. Any clue? Ok, the test passed after a retry. Flaky test? Also, Oozie started fine after that (although security is disabled for now, so maybe I just haven't run into any potential runtime problems yet). Thx, /Maxime -- Maxime Petazzoni, Platform Engineer at Turn, Inc (www.turn.com)
