[
https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102600#comment-13102600
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-2978:
----------------------------------------------------
I committed this patch to trunk, and resubmitted MAPREDUCE-2675 to Jenkins.
Left this ticket unresolved to wait for Jenkins' confirmation on one of the
patches.
*It's been more than an hour since the resubmit, but Jenkins hasn't returned
since.* I'm afraid I may have bombed Jenkins with this patch. If I don't give
any more update my time (IST), and Jenkins still doesn't come back, this patch
can be a potential suspect and offers itself for a revert.
> 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
