[
https://issues.apache.org/jira/browse/OOZIE-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720087#comment-16720087
]
Julia Kinga Marton edited comment on OOZIE-3401 at 12/13/18 12:14 PM:
----------------------------------------------------------------------
I have played a little bit with this test case. Below are my findings:
* During a _mvn install_ the resources are copied to target directory. If I
run the test after a _mvn install_, it passed. If I run _mvn clean test_ it
failed because the target directory is deleted and the resources are missing.
This explains why the test is passing during precommit runs.
* If I tried to run the test after applying the patch without doing an install
before it, it still failed.
I think that the root problem here is that the resource copy is defined in a
phase what is not executed when running just _mvn test_.
was (Author: kmarton):
I have played a little bit with this test case. Below are my findings:
* During a _mvn install_ the resources are copied to target directory. If I
run the test after a _mvn install_, it passed. If I run _mvn clean test_ it
failed because the target directory is deleted and the resources are missing.
This explains why the test is passing during precommit runs.
* If I tried to run the test after applying the patch without doing an install
before it, it still failed. I think that the root problem here is that the
resource copy if defined in a phase what is not executed when running just _mvn
test_.
> TestPySpark failure
> -------------------
>
> Key: OOZIE-3401
> URL: https://issues.apache.org/jira/browse/OOZIE-3401
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Affects Versions: trunk
> Reporter: Andras Salamon
> Assignee: Andras Salamon
> Priority: Major
> Fix For: 5.2.0
>
> Attachments: OOZIE-3401-01.patch
>
>
> [TestPySpark|https://github.com/apache/oozie/blob/master/sharelib/spark/src/test/java/org/apache/oozie/action/hadoop/TestPyspark.java]
> fails with the following error:
> {noformat}[INFO] Running org.apache.oozie.action.hadoop.TestPyspark
> [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 131.97 s <<< FAILURE! - in org.apache.oozie.action.hadoop.TestPyspark
> [ERROR] testPyspark(org.apache.oozie.action.hadoop.TestPyspark) Time
> elapsed: 131.97 s <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<[SUCCEED]ED> but
> was:<[FAILED/KILL]ED>
> at junit.framework.Assert.assertEquals(Assert.java:100)
> at junit.framework.Assert.assertEquals(Assert.java:107)
>
> at junit.framework.TestCase.assertEquals(TestCase.java:269)
> at
> org.apache.oozie.action.hadoop.TestPyspark.testPysparkHelper(TestPyspark.java:107)
> at
> org.apache.oozie.action.hadoop.TestPyspark.testPyspark(TestPyspark.java:85)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
>
> at junit.framework.TestCase.runTest(TestCase.java:176)
>
> at junit.framework.TestCase.runBare(TestCase.java:141)
>
> at junit.framework.TestResult$1.protect(TestResult.java:122)
>
> at junit.framework.TestResult.runProtected(TestResult.java:142)
>
> at junit.framework.TestResult.run(TestResult.java:125)
>
> at junit.framework.TestCase.run(TestCase.java:129)
>
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
>
> at junit.framework.TestSuite.run(TestSuite.java:250)
>
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.junit.runners.Suite.runChild(Suite.java:127)
>
> at org.junit.runners.Suite.runChild(Suite.java:26)
>
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler$1.run(Scheduler.java:410)
> at
> org.apache.maven.surefire.junitcore.pc.InvokerStrategy.schedule(InvokerStrategy.java:54)
> at
> org.apache.maven.surefire.junitcore.pc.Scheduler.schedule(Scheduler.java:367)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>
>
> at
> org.apache.maven.surefire.junitcore.pc.ParallelComputerBuilder$PC$1.run(ParallelComputerBuilder.java:593)
> at
> org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
>
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
>
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at
> org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:373)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:334)
>
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:119)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:407)
> {noformat}
> The test runs successfully in the precommit unit tests:
> https://builds.apache.org/job/PreCommit-OOZIE-Build/944/consoleFull
> The bug was most likely introduced in OOZIE-3321
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
