[
https://issues.apache.org/jira/browse/HADOOP-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798594#action_12798594
]
Hadoop QA commented on HADOOP-6374:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12429870/HADOOP-6374.patch
against trunk revision 897023.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/268/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/268/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/268/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/268/console
This message is automatically generated.
> JUnit tests should never depend on anything in conf
> ---------------------------------------------------
>
> Key: HADOOP-6374
> URL: https://issues.apache.org/jira/browse/HADOOP-6374
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Owen O'Malley
> Assignee: Anatoli Fomenko
> Priority: Blocker
> Attachments: HADOOP-6374.patch
>
>
> The recent change to mapred-queues.xml that causes many mapreduce tests to
> break unless you delete conf/mapred-queues.xml out of your build tree is bad.
> We need to make sure that nothing in conf is used in the unit tests. One
> potential solution is to copy the templates into build/test/conf and use that
> instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
