[
https://issues.apache.org/jira/browse/HADOOP-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717007#action_12717007
]
Hadoop QA commented on HADOOP-5970:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12409855/hadoop-5970.patch
against trunk revision 782083.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 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 Eclipse classpath. The patch retains Eclipse classpath integrity.
+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 failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/475/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/475/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/475/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/475/console
This message is automatically generated.
> TestJobInProgress brings up MinMR/DFS clusters for every test
> -------------------------------------------------------------
>
> Key: HADOOP-5970
> URL: https://issues.apache.org/jira/browse/HADOOP-5970
> Project: Hadoop Core
> Issue Type: Test
> Components: test
> Reporter: Jothi Padmanabhan
> Assignee: Jothi Padmanabhan
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: hadoop-5970.patch
>
>
> TestJobInProgress brings up MiniMR clusters in setUp and brings it down in
> tearDown methods. Since these methods are called before each test, the test
> brings up/down the cluster several times. Instead, the cluster should just be
> brought up once, all tests run and then brought down
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
