hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2978) hudson findbugs not reporting properly
Date Mon, 12 Sep 2011 11:11:08 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vinod Kumar Vavilapalli updated MAPREDUCE-2978:

    Status: Open  (was: Patch Available)

Forcing Jenkins to use test-patch to test changes test-patches! I must be dreaming!

Cancelling the patch to incorporate one more minor change: Jenkins prints the links to findBugs
warning even when there are none.

> 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.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


View raw message