[
https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved MAPREDUCE-2978.
------------------------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
bq. 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
Okay Amareshwari figured this one out by reattaching the same patch to
MAPREDUCE-2979. Jenkins duly performed his duty.
She says:
bq. https://builds.apache.org/job/PreCommit-Admin/ : see how to trigger. The
combination of a Jira being in Patch Available state AND having a new
attachment that has never been processed by this system is what will trigger a
new test of the patch.
Something new for the day, thanks Amareshwari!
Closing this as resolved.
> 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
