[
https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13101610#comment-13101610
]
Tom White commented on MAPREDUCE-2978:
--------------------------------------
Looking in the console, it did find the findbugs violation (
https://builds.apache.org/view/G-L/view/Hadoop/job/PreCommit-MapReduce-Build/662/console):
{noformat}
Found 1 Findbugs warnings
(/home/jenkins/jenkins-slave/workspace/PreCommit-MAPREDUCE-Build/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/findbugsXml.xml)
{noformat}
The fact it didn't report it is probably because the number in
hadoop-mapreduce-project/dev-support/test-patch.properties is higher than 1. It
should be changed to be zero.
I'll take a look at fixing this issue.
> 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
> Fix For: 0.24.0
>
>
> 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
