[jira] [Commented] (HIVE-6774) "Not a valid JAR" errors from TestExecDriver

["Jason Dere (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-6774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951324#comment-13951324 ] 

Jason Dere commented on HIVE-6774:
----------------------------------

Looks like the test is relying on the hive-exec JAR being installed to the local maven repository, and it's not there yet during the maven test phase.  [~brocknoland], would it be more appropriate for TestExecDriver to be added to itests? Or is it expected to run "mvn clean install -DskipTests" before actually running any tests?

> "Not a valid JAR" errors from TestExecDriver
> --------------------------------------------
>
>                 Key: HIVE-6774
>                 URL: https://issues.apache.org/jira/browse/HIVE-6774
>             Project: Hive
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jason Dere
>
> If I wipe out my local Maven repository and run the command:
> mvn clean install -Dtest=TestExecDriver -Phadoop-1
> All of the TestExecDriver tests fail with the following errors:
> {noformat}
> Not a valid JAR: /Users/jdere/.m2/repository/org/apache/hive/hive-exec/0.14.0-SNAPSHOT/hive-exec-0.14.0-SNAPSHOT.jar
> Execution failed with exit status: 255
> Obtaining error information
> Task failed!
> Task ID:
>   null
> Logs:
> /Users/jdere/dev/hive.git/ql/target/tmp/log/hive.log
> java.lang.NullPointerException
>         at org.apache.hadoop.hive.ql.session.SessionState.addLocalMapRedErrors(SessionState.java:919)
>         at org.apache.hadoop.hive.ql.exec.mr.MapRedTask.execute(MapRedTask.java:282)
>         at org.apache.hadoop.hive.ql.exec.TestExecDriver.executePlan(TestExecDriver.java:460)
>         at org.apache.hadoop.hive.ql.exec.TestExecDriver.testMapPlan1(TestExecDriver.java:474)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at junit.framework.TestCase.runTest(TestCase.java:168)
>         at junit.framework.TestCase.runBare(TestCase.java:134)
>         at junit.framework.TestResult$1.protect(TestResult.java:110)
>         at junit.framework.TestResult.runProtected(TestResult.java:128)
>         at junit.framework.TestResult.run(TestResult.java:113)
>         at junit.framework.TestCase.run(TestCase.java:124)
>         at junit.framework.TestSuite.runTest(TestSuite.java:243)
>         at junit.framework.TestSuite.run(TestSuite.java:238)
>         at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>         at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
>         at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>         at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>         at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)