[
https://issues.apache.org/jira/browse/MAPREDUCE-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805262#action_12805262
]
Steve Loughran commented on MAPREDUCE-1414:
-------------------------------------------
Hudson tests failing w/ ClassNotFound:
{code}
java.lang.NoClassDefFoundError: org/apache/hadoop/net/StaticMapping
at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:288)
at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:132)
at
org.apache.hadoop.mapred.ClusterMapReduceTestCase.startCluster(ClusterMapReduceTestCase.java:81)
at
org.apache.hadoop.mapred.ClusterMapReduceTestCase.setUp(ClusterMapReduceTestCase.java:56)
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.StaticMapping
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
{code}
Looking at the missing class, it is a test class in hadoop-common, and is not
in hadoop-common.jar. I could easily imagine that the classpath for Hudson
isn't picking up the test jar wherever it is meant to
> TestRecoveryManager can spin waiting for a job to be half done
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-1414
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1414
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 0.22.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1414.patch
>
>
> This is something I've seen: the TestRecoveryManager spinning forever waiting
> for a job to get half done. The test runner will eventually kill it, but that
> loses any log and chance of finding the problem.
> Solution: have a timeout on how long you wait for the job
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
