Hello Abhishek, Rohini helped me fix OOZIE-2536 - Hadoop's cleanup of local directory in uber mode causing failures. If it is ok to include this fix into our 4.3.0 release, could you please include it? It is an important issue in the sense that hadoop was deleting configuration properties (propagation-conf.xml) which we put intentionally for OOZIE-2129.
Another update on test failures. I have created OOZIE-2721 and OOZIE-2720. I have put a patch for OOZIE-2720. On Sat, Oct 29, 2016 at 2:18 PM, Peter Cseh <[email protected]> wrote: > Hi there, > > - signature, checksums, license are looking ok > - with Attila's command: mvn clean package assembly:single > -DjavaVersion=1.8 -DtargetVersion=1.8 > -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor > -Phadoop-2 -Dhadoop.version=2.6.0 -Puber > On Java 1.8u77, only one test is failing for me: > testUpdateConfForTimeLineServiceEnabled(org.apache.oozie.act > ion.hadoop.TestJavaActionExecutor): expected:<[tru]e> but was:<[fals]e> > > The tests are passing wth Hadoop 2.4, I'm attaching an output of a > successful build with hadoop 2.4 with no failing tests after applying > OOZIE-2719. The tests are quite stable on Hadoop 2.4, I had 3-4 runs with > no failures. > > > - Hadoop-1: The command mvn clean package assembly:single -fn > -DjavaVersion=1.8 -DtargetVersion=1.8 -Phadoop-1 -Puber fails with the > following error: > [ERROR] Failed to execute goal on project oozie-sharelib-streaming: Could > not resolve dependencies for project > org.apache.oozie:oozie-sharelib-streaming:jar:4.3.0: > Failed to collect dependencies at > org.apache.hadoop:hadoop-streaming:jar:1.2.1: > Failed to read artifact descriptor for > org.apache.hadoop:hadoop-streaming:jar:1.2.1: > Could not transfer artifact org.apache.hadoop:hadoop-streaming:pom:1.2.1 > from/to central (http://repo1.maven.org/maven2): Operation timed out > (Read failed) -> [Help 2] > [ERROR] Failed to execute goal on project oozie-examples: Could not > resolve dependencies for project org.apache.oozie:oozie-examples:jar:4.3.0: > Could not find artifact org.apache.oozie:oozie-sharelib-streaming:jar:4.3.0 > in central (http://repo1.maven.org/maven2) -> [Help 2] > [ERROR] Failed to execute goal on project oozie-sharelib-spark: Could not > resolve dependencies for project > org.apache.oozie:oozie-sharelib-spark:jar:4.3.0: > The following artifacts could not be resolved: > org.apache.oozie:oozie-examples:jar:4.3.0, > org.apache.oozie:oozie-sharelib-streaming:jar:4.3.0: Could not find > artifact org.apache.oozie:oozie-examples:jar:4.3.0 in central ( > http://repo1.maven.org/maven2) -> [Help 2] > [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-dependency-plugin:2.4:copy (copy-sharelib) on project oozie-webapp: > Unable to find artifact. Failure to find > org.apache.oozie:oozie-sharelib-streaming:jar:4.3.0 > in http://repo1.maven.org/maven2 was cached in the local repository, > resolution will not be reattempted until the update interval of central has > elapsed or updates are forced > > gp > > > > > On Sat, Oct 29, 2016 at 4:45 AM, Abhishek Bafna <[email protected]> > wrote: > >> Hi Satish, >> >> I am not able to re produce two other test failure, neither with jdk7 nor >> jdk8. Please do create a jira with failure exception. >> >> Thanks. >> >> On Saturday 29 October 2016, Robert Kanter <[email protected]> wrote: >> >> > While we should definitely eventually address the failures Attila saw >> with >> > Hadoop 2.6.0; I think the minimum for an Oozie 4.3.0 release should be >> to >> > have no test failures with Hadoop 2.4.0 (the default). We tend to have >> a >> > lot of flakey tests that we ignore during development, and this might >> be a >> > good impetus to force ourselves to fix them. >> > >> > - Robert >> > >> > On Fri, Oct 28, 2016 at 4:29 PM, satish saley <[email protected] >> > <javascript:;>> >> > wrote: >> > >> > > Hi, >> > > >> > > I see three test failures, will create a jira. >> > > >> > > >> > > testForkJoinMismatch(org.apache.oozie.workflow.lite. >> > > TestLiteWorkflowAppParser) >> > > [OOZIE-2719] >> > > >> > > >> > > testActionKillCommandDate(org.apache.oozie.command.coord. >> > > TestCoordActionsKillXCommand): >> > > expected:<RUNNING> but was:<KILLED> >> > > >> > > >> > > testMaxMatThrottleNotPicked(org.apache.oozie.service. >> > > TestCoordMaterializeTriggerService): >> > > expected:<Fri Oct 28 13:33:38 PDT 2016> but was:<Fri Oct 28 13:33:40 >> PDT >> > > 2016> >> > > >> > > On Fri, Oct 28, 2016 at 3:26 AM, Attila Sasvari < >> [email protected] >> > <javascript:;>> >> > > wrote: >> > > >> > > > Update: JavaActionExecutor tests seem to always fail with hadoop >> 2.6.0 >> > , >> > > > with 2.4.0 these tests pass. >> > > > >> > > > On Fri, Oct 28, 2016 at 11:22 AM, Attila Sasvari < >> > [email protected] <javascript:;>> >> > > > wrote: >> > > > >> > > > > Hi there, >> > > > > >> > > > > I also downloaded it and tried to build it with running the >> > > > > JavaActionExecutor tests: >> > > > > >> > > > > mvn clean package assembly:single -DjavaVersion=1.8 >> > -DtargetVersion=1.7 >> > > > > -Dtest=org.apache.oozie.action.hadoop.TestJavaActionExecutor >> > > -Phadoop-2 >> > > > > -Dhadoop.version=*2.6.0* -Puber >> > > > > >> > > > > >> > > > > Failed tests: testSimpestSleSubmitOK(org.apa >> > > > > che.oozie.action.hadoop.TestJavaActionExecutor) >> > > > > testOutputSubmitOK(org.apache.oozie.action.hadoop.TestJavaAc >> > > > > tionExecutor) >> > > > > testIdSwapSubmitOK(org.apache.oozie.action.hadoop.TestJavaAc >> > > > > tionExecutor) >> > > > > testAdditionalJarSubmitOK(org.apache.oozie.action.hadoop.Tes >> > > > > tJavaActionExecutor) >> > > > > testExit0SubmitOK(org.apache.oozie.action.hadoop. >> > > > TestJavaActionExecutor) >> > > > > testExit1SubmitError(org.apache.oozie.action.hadoop.TestJava >> > > > > ActionExecutor) >> > > > > testChildKill(org.apache.oozie.action.hadoop. >> > > TestJavaActionExecutor): >> > > > > expected:<1> but was:<0> >> > > > > testExceptionSubmitException(org.apache.oozie.action.hadoop. >> > > > > TestJavaActionExecutor) >> > > > > testExceptionSubmitThrowable(org.apache.oozie.action.hadoop. >> > > > > TestJavaActionExecutor) >> > > > > testRecovery(org.apache.oozie.action.hadoop. >> > TestJavaActionExecutor): >> > > > > expected:<...ob_1477579833383_001[1]> but >> > > was:<...ob_1477579833383_001[ >> > > > 2]> >> > > > > testPrepare(org.apache.oozie.action.hadoop.TestJavaActionEx >> ecutor) >> > > > > testUpdateConfForTimeLineServiceEnabled(org.apache.oozie.act >> > > > > ion.hadoop.TestJavaActionExecutor): expected:<[tru]e> but >> > > was:<[fals]e> >> > > > > testActionShareLibWithNonDefaultNamenode(org.apache.oozie.ac >> > > > > tion.hadoop.TestJavaActionExecutor) >> > > > > testJobSubmissionWithoutYarnKill(org.apache.oozie.action.had >> > > > > oop.TestJavaActionExecutor) >> > > > > >> > > > > Tests run: 46, Failures: 14, Errors: 0, Skipped: 0 >> > > > > >> > > > > (using OS X 10.11.6 (15G1004), java 1.8.0_101) >> > > > > >> > > > > Regards, >> > > > > - Attila >> > > > > >> > > > > ps: I am re-running the tests to verify it is not a sporadic >> problem >> > > that >> > > > > is specific to my local dev environment. >> > > > > >> > > > > >> > > > > On Tue, Oct 25, 2016 at 7:38 AM, Abhishek Bafna < >> > [email protected] <javascript:;>> >> > > > > wrote: >> > > > > >> > > > >> Hi, >> > > > >> >> > > > >> I have created a build for Oozie 4.3.0, candidate 0. >> > > > >> >> > > > >> Keys to verify the signature of the release artifact are >> available >> > at >> > > > >> >> > > > >> http://www.apache.org/dist/oozie/KEYS >> > > > >> >> > > > >> Please download, test, and try it out: >> > > > >> >> > > > >> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/ >> > > > >> >> > > > >> The release, md5 signature, gpg signature, and rat report can all >> > > > >> be found at the above address. >> > > > >> >> > > > >> Vote closes on [Sat Oct 29 11:00:00 IST 2016]. >> > > > >> >> > > > >> Thanks! >> > > > >> Abhishek Bafna >> > > > >> >> > > > > >> > > > > >> > > > >> > > >> > >> > > > > -- > Peter Cseh > Software Engineer > <http://www.cloudera.com> >
