hadoop-mapreduce-issues mailing list archives

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

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102518#comment-13102518

Hadoop QA commented on MAPREDUCE-2978:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/703//console

This message is automatically generated.

> 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