Jira: https://issues.apache.org/jira/browse/OOZIE-3513
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1142/
###################################################################################
########################## LAST 100 LINES OF THE CONSOLE
###########################
[...truncated 2.09 MB...]
Testing JIRA OOZIE-3513
Cleaning local git workspace
----------------------------
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any star imports
-1 the patch contains 2 line(s) longer than 132 characters
+1 the patch adds/modifies 5 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 Javadoc generation succeeded with the patch
+1 the patch does not seem to introduce new Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
-1 There are [21] new bugs found below threshold in total that must be fixed.
+1 There are no new bugs found in [sharelib/hive2].
+1 There are no new bugs found in [sharelib/spark].
+1 There are no new bugs found in [sharelib/oozie].
+1 There are no new bugs found in [sharelib/pig].
+1 There are no new bugs found in [sharelib/streaming].
+1 There are no new bugs found in [sharelib/hive].
+1 There are no new bugs found in [sharelib/distcp].
+1 There are no new bugs found in [sharelib/hcatalog].
+1 There are no new bugs found in [sharelib/sqoop].
+1 There are no new bugs found in [sharelib/git].
+1 There are no new bugs found in [client].
+1 There are no new bugs found in [docs].
-1 There are [15] new bugs found below threshold in [tools] that must be
fixed, listing only the first [5] ones.
You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
The top [5] most important SpotBugs errors are:
At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
+1 There are no new bugs found in [fluent-job/fluent-job-api].
+1 There are no new bugs found in [server].
+1 There are no new bugs found in [webapp].
+1 There are no new bugs found in [examples].
-1 There are [6] new bugs found below threshold in [core] that must be
fixed, listing only the first [5] ones.
You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
The top [5] most important SpotBugs errors are:
At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run : 3168
Tests failed : 0
Tests in error : 3
Tests timed out : 0
-1 [ERROR] There are [3] test errors in [core]. Listing only the first [5] ones
testVerifyParametersNull:org.apache.oozie.util.TestParameterVerifier
Check console output for the full list of errors/failures
Tests failed at first run:
TestPurgeXCommand#testPurgeableBundleUnpurgeableCoordinatorUnpurgeableWorkflow
TestPurgeXCommand#testPurgeableWorkflowPurgeableSubWorkflowPurgeableSubSubWorkflow
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
-1 Overall result, please check the reported -1(s)
The full output of the test-patch run is available at
https://builds.apache.org/job/PreCommit-OOZIE-Build/1142/
Adding comment to JIRA
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
0100 5282 0 0 100 5282 0 4686 0:00:01 0:00:01 --:--:--
4686{"self":"https://issues.apache.org/jira/rest/api/2/issue/13237960/comment/16857845","id":"16857845","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA
OOZIE-3513\n\nCleaning local git
workspace\n\n----------------------------\n\n{color:green}+1
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:red}-1
RAW_PATCH_ANALYSIS{color}\n. {color:green}+1{color} the patch does not
introduce any @author tags\n. {color:green}+1{color} the patch does not
introduce any tabs\n. {color:green}+1{color} the patch does not introduce
any trailing spaces\n. {color:green}+1{color} the patch does not introduce
any star imports\n. {color:red}-1{color} the patch contains 2 line(s) longer
than 132 characters\n. {color:green}+1{color} the patch adds/modifies 5
testcase(s)\n{color:green}+1 RAT{color}\n. {color:green}+1{color} the patch
does not seem to introduce new RAT warnings\n{color:green}+1 JAVADOC{color}\n.
{color:green}+1{color} Javadoc generation succeeded with the patch\n.
{color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)\n{color:green}+1 COMPILE{color}\n. {color:green}+1{color} HEAD
compiles\n. {color:green}+1{color} patch compiles\n.
{color:green}+1{color} the patch does not seem to introduce new javac
warnings\n{color:red}-1{color} There are [21] new bugs found below threshold in
total that must be fixed.\n. {color:green}+1{color} There are no new bugs
found in [sharelib/hive2].\n. {color:green}+1{color} There are no new bugs
found in [sharelib/spark].\n. {color:green}+1{color} There are no new bugs
found in [sharelib/oozie].\n. {color:green}+1{color} There are no new bugs
found in [sharelib/pig].\n. {color:green}+1{color} There are no new bugs
found in [sharelib/streaming].\n. {color:green}+1{color} There are no new
bugs found in [sharelib/hive].\n. {color:green}+1{color} There are no new
bugs found in [sharelib/distcp].\n. {color:green}+1{color} There are no new
bugs found in [sharelib/hcatalog].\n. {color:green}+1{color} There are no
new bugs found in [sharelib/sqoop].\n. {color:green}+1{color} There are no
new bugs found in [sharelib/git].\n. {color:green}+1{color} There are no new
bugs found in [client].\n. {color:green}+1{color} There are no new bugs
found in [docs].\n. {color:red}-1{color} There are [15] new bugs found below
threshold in [tools] that must be fixed, listing only the first [5] ones.\n.
You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html\n. The top [5] most important SpotBugs errors
are:\n. At OozieDBCLI.java:[line 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection\n. At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]\n.
At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]\n. At
OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]\n. At
OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]\n.
{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].\n. {color:green}+1{color} There are no new bugs
found in [server].\n. {color:green}+1{color} There are no new bugs found in
[webapp].\n. {color:green}+1{color} There are no new bugs found in
[examples].\n. {color:red}-1{color} There are [6] new bugs found below
threshold in [core] that must be fixed, listing only the first [5] ones.\n.
You can find the SpotBugs diff here (look for the red and orange ones):
core/fi100 11940 0 6658 100 5282 5905 4684 0:00:01 0:00:01 --:--:--
5907
ndbugs-new.html\n. The top [5] most important SpotBugs errors are:\n. At
BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection\n. At BulkJPAExecutor.java:[line
176]: At BulkJPAExecutor.java:[line 175]\n. At BulkJPAExecutor.java:[line
205]: At BulkJPAExecutor.java:[line 199]\n. This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]\n.
At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line
127]\n{color:green}+1 BACKWARDS_COMPATIBILITY{color}\n.
{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations\n. {color:green}+1{color} the
patch does not modify JPA files\n{color:red}-1 TESTS{color}\n. Tests run
: 3168\n. Tests failed : 0\n. Tests in error : 3\n. Tests
timed out : 0\n\n{color:red}-1{color} [ERROR] There are [3] test errors in
[core]. Listing only the first [5]
ones\ntestVerifyParametersNull:org.apache.oozie.util.TestParameterVerifier\n\nCheck
console output for the full list of errors/failures\n. {color:orange}Tests
failed at first
run:{color}\nTestPurgeXCommand#testPurgeableBundleUnpurgeableCoordinatorUnpurgeableWorkflow\nTestPurgeXCommand#testPurgeableWorkflowPurgeableSubWorkflowPurgeableSubSubWorkflow\n.
For the complete list of flaky tests, see TEST-SUMMARY-FULL
files.\n{color:green}+1 DISTRO{color}\n. {color:green}+1{color} distro
tarball builds with the patch \n\n----------------------------\n{color:red}*-1
Overall result, please check the reported -1(s)*{color}\n\n\nThe full output of
the test-patch run is available at\n\n.
https://builds.apache.org/job/PreCommit-OOZIE-Build/1142/\n\n","updateAuthor":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
QA","active":true,"timeZone":"Etc/UTC"},"created":"2019-06-06T16:25:08.358+0000","updated":"2019-06-06T16:25:08.358+0000"}
test-patch exit code: 1
Build step 'Execute shell' marked build as failure
[description-setter] Description set: OOZIE-3513
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###################################################################################
############################## FAILED TESTS (if any)
##############################
3 tests failed.
FAILED: org.apache.oozie.util.TestParamChecker.testNotNullElements
Error Message:
name cannot be null
Stack Trace:
java.lang.NullPointerException: name cannot be null
at java.util.Objects.requireNonNull(Objects.java:228)
at
org.apache.oozie.util.ParamChecker.notEmptyElements(ParamChecker.java:75)
at
org.apache.oozie.util.TestParamChecker.testNotNullElements(TestParamChecker.java:32)
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:590)
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:158)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
FAILED: org.apache.oozie.util.TestParameterVerifier.testVerifyParametersNull
Error Message:
conf cannot be null
Stack Trace:
java.lang.NullPointerException: conf cannot be null
at java.util.Objects.requireNonNull(Objects.java:228)
at
org.apache.oozie.util.ParameterVerifier.verifyParameters(ParameterVerifier.java:50)
at
org.apache.oozie.util.TestParameterVerifier.testVerifyParametersNull(TestParameterVerifier.java:42)
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:590)
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:158)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
FAILED: org.apache.oozie.util.TestPriorityDelayQueue.testQueueElement
Error Message:
element cannot be null
Stack Trace:
java.lang.NullPointerException: element cannot be null
at java.util.Objects.requireNonNull(Objects.java:228)
at
org.apache.oozie.util.TestPriorityDelayQueue$TestQueueElement.<init>(TestPriorityDelayQueue.java:426)
at
org.apache.oozie.util.TestPriorityDelayQueue.testQueueElement(TestPriorityDelayQueue.java:58)
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:590)
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:158)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
