[
https://issues.apache.org/jira/browse/HADOOP-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270833#comment-13270833
]
Hadoop QA commented on HADOOP-8354:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12526041/HADOOP-8354.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+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 eclipse:eclipse. The patch built with eclipse:eclipse.
+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 unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/962//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/962//console
This message is automatically generated.
> test-patch findbugs may fail if a dependent module is changed
> -------------------------------------------------------------
>
> Key: HADOOP-8354
> URL: https://issues.apache.org/jira/browse/HADOOP-8354
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Tom White
> Assignee: Robert Joseph Evans
> Attachments: HADOOP-8354.txt
>
>
> This can happen when code in a dependent module is changed, but the change
> isn't picked up. E.g.
> https://issues.apache.org/jira/browse/MAPREDUCE-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266867#comment-13266867
> We can fix this by running 'mvn install -DskipTests
> -Dmaven.javadoc.skip=true' first.
--
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