[
https://issues.apache.org/jira/browse/HADOOP-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996871#comment-12996871
]
Hadoop QA commented on HADOOP-7068:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12466509/hadoop-7068-trunk-v2.patch
against trunk revision 1071364.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+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 (version 1.3.9)
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.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/251//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/251//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/251//console
This message is automatically generated.
> Ivy resolve force mode should be turned off by default
> ------------------------------------------------------
>
> Key: HADOOP-7068
> URL: https://issues.apache.org/jira/browse/HADOOP-7068
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Luke Lu
> Assignee: Luke Lu
> Attachments: hadoop-7068-trunk-v1.patch, hadoop-7068-trunk-v2.patch
>
>
> The problem is introduced by HADOOP-6486. Which have caused a lot of
> mysterious artifact issues (unable to downgrade or do parallel dev, without
> wiping out both m2 and ivy caches etc.) wasting countless hours of dev (many
> people's) time to track down the issue.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
