[
https://issues.apache.org/jira/browse/MAPREDUCE-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252578#comment-13252578
]
Thomas Graves commented on MAPREDUCE-4142:
------------------------------------------
All of these tests have @Ignore in them and if run individually have been
failing for a long time before the listed jiras.
I was running them with: ant test -Dtestcase=foo so I'm not sure why that isn't
honoring the @Ignore.
Checking a jenkins output of running all the tests shows:
[junit] Running org.apache.hadoop.mapred.TestRecoveryManager
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.043 sec
[junit] Running org.apache.hadoop.mapred.TestJobTrackerSafeMode
[junit] Tests run: 0, Failures: 0, Errors: 0, Time elapsed: 0.042 sec
...
I'm running a full test run now to verify that holds.
> MR test failures on branch-1
> ----------------------------
>
> Key: MAPREDUCE-4142
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4142
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Eli Collins
> Assignee: Thomas Graves
>
> The following test classes are failing on branch-1:
> TestJobTrackerRestartWithLostTracker, TestJobTrackerSafeMode,
> TestMiniMRMapRedDebugScript, TestRecoveryManager, TestTaskTrackerLocalization.
> Recent MR changes, believe these tests were passing before these failures:
> - MAPREDUCE-4012 Hadoop Job setup error leaves no useful info to users. (tgrav
> - MAPREDUCE-1238. mapred metrics shows negative count of waiting maps and redu
> - MAPREDUCE-4017. Add jobname to jobsummary log (tgraves and Koji Noguchi via
> - MAPREDUCE-4003. log.index (No such file or directory) AND Task process exit
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
