[
https://issues.apache.org/jira/browse/HADOOP-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639324#action_12639324
]
Hemanth Yamijala commented on HADOOP-4378:
------------------------------------------
The issue is related to HADOOP-4409. All tests using {{TestMiniMRWithDFS}}
could be potentially affected. However, the way the class is used, none of the
other tests are actually failing except {{TestJobQueueInformation}}. I propose
we fix this test case to not use {{TestMiniMRWithDFS}}, as it really doesn't
need to run any specific type of job, nor check for correctness of job running
aspects. Instead, it could use a simple job like the {{SleepJob}}.
The real cause for failure can be tracked in HADOOP-4409. I think the mapred
team needs to make a call on whether this is a blocker.
> TestJobQueueInformation fails regularly
> ---------------------------------------
>
> Key: HADOOP-4378
> URL: https://issues.apache.org/jira/browse/HADOOP-4378
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred, test
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Sreekanth Ramakrishnan
> Priority: Blocker
> Fix For: 0.19.0
>
> Attachments: 4378_20081010TestJobQueueInformation.txt
>
>
> Got the same result from Linux and Windows:
> {noformat}
> Testcase: testJobQueues took 40.806 sec
> FAILED
> task tracker dir
> /home/tsz/hadoop/latest/build/test/mapred/local/1_0/taskTrackerr does not
> exist.
> junit.framework.AssertionFailedError: task tracker dir
> /home/tsz/hadoop/latest/build/test/mapred/local/1_0/taskTracker does not
> exist.
> at
> org.apache.hadoop.mapred.TestMiniMRWithDFS.checkTaskDirectories(TestMMiniMRWithDFS.java:140)
> at
> org.apache.hadoop.mapred.TestMiniMRWithDFS.runWordCount(TestMiniMRWitthDFS.java:196)
> at
> org.apache.hadoop.mapred.TestJobQueueInformation.testJobQueues(TestJoobQueueInformation.java:90)
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
