[
https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102561#comment-13102561
]
Hudson commented on MAPREDUCE-2978:
-----------------------------------
Integrated in Hadoop-Common-trunk-Commit #870 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/870/])
MAPREDUCE-2978. Fixed test-patch to make Jenkins report findbugs warnings
properly. Contributed by Tom White.
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1169696
Files :
* /hadoop/common/trunk/dev-support/test-patch.sh
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/dev-support/test-patch.properties
> hudson findbugs not reporting properly
> --------------------------------------
>
> Key: MAPREDUCE-2978
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2978
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 0.24.0
> Reporter: Thomas Graves
> Assignee: Tom White
> Fix For: 0.24.0
>
> Attachments: MAPREDUCE-2978-20110912.txt, MAPREDUCE-2978.patch
>
>
> It seems that hudson is not properly reporting findbug failures introduced by
> jiras.
> Here is an example where hudson gave the jira a +1 for findbugs but it really
> introduced a bug:
> https://issues.apache.org/jira/browse/MAPREDUCE-2937
> The actual findbugs report - you'll see there is 1:
> https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/662//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-jobclient.html
> Note that I had to enter in the extra path of hadoop-mapreduce-project to see
> the html file so perhaps the path it is using to do the diff is wrong.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
