[
https://issues.apache.org/jira/browse/MAPREDUCE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726917#comment-13726917
]
Hadoop QA commented on MAPREDUCE-5440:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595483/MAPREDUCE-5440.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-tools/hadoop-distcp.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3928//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3928//console
This message is automatically generated.
> TestCopyCommitter Fails on JDK7
> -------------------------------
>
> Key: MAPREDUCE-5440
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5440
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: trunk, 2.3.0
> Reporter: Robert Parker
> Assignee: Robert Parker
> Attachments: MAPREDUCE-5440.patch
>
>
> The testNoCommitAction is affected by the testPreserveStatus. The
> testPreserveStatus leaves the CONF_LABEL_PRESERVE_STATUS set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
