[OOZIE-1733] Fix test failures caused by OOZIE-1722

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 06/Mar/14 19:41
• Updated: 09/Dec/14 00:45
• Resolved: 10/Mar/14 16:43

Description

Some of the tests are failing due to OOZIE-1722 when run against a version of Hadoop that supports tags.

Affected tests are:

• TestMapReduceMain
• TestHiveMain
• TestPigMain
• TestStreamingMain

java.lang.RuntimeException: Could not find Oozie job launch time
	at org.apache.oozie.action.hadoop.LauncherMainHadoopUtils.getChildYarnJobs(LauncherMainHadoopUtils.java:48)
	at org.apache.oozie.action.hadoop.LauncherMainHadoopUtils.getYarnJobForMapReduceAction(LauncherMainHadoopUtils.java:74)
	at org.apache.oozie.action.hadoop.MapReduceMain.run(MapReduceMain.java:51)
	at org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:38)
	at org.apache.oozie.action.hadoop.MapReduceMain.main(MapReduceMain.java:37)
	at org.apache.oozie.action.hadoop.TestMapReduceMain.call(TestMapReduceMain.java:67)
	at org.apache.oozie.action.hadoop.TestMapReduceMain.call(TestMapReduceMain.java:30)
	at org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:32)
	at org.apache.oozie.action.hadoop.MainTestCase$1.run(MainTestCase.java:30)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:415)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1548)
	at org.apache.oozie.action.hadoop.MainTestCase.execute(MainTestCase.java:30)
	at org.apache.oozie.action.hadoop.MainTestCase.testMain(MainTestCase.java:39)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	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.junitcore.ClassDemarcatingRunner.run(ClassDemarcatingRunner.java:58)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:24)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
Caused by: java.lang.NumberFormatException: null
	at java.lang.Long.parseLong(Long.java:404)
	at java.lang.Long.parseLong(Long.java:483)
	at org.apache.oozie.action.hadoop.LauncherMainHadoopUtils.getChildYarnJobs(LauncherMainHadoopUtils.java:46)
	... 36 more

The cause is fairly trivial, its because of how those tests are running the Main classes without calling the methods that set the properties added in OOZIE-1722