You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2010/12/12 18:35:00 UTC

[jira] Assigned: (ZOOKEEPER-929) hudson qabot incorrectly reporting issues as number 909 when the patch from 908 is the one being tested

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

Nigel Daley reassigned ZOOKEEPER-929:
-------------------------------------

    Assignee: Patrick Hunt  (was: Nigel Daley)

Patrick, have u seen this again?  If not, let's close it.

> hudson qabot incorrectly reporting issues as number 909 when the patch from 908 is the one being tested
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-929
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-929
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: build
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>
> Hi Nigel can you take a look at this?
> Following you'll see the email I got, notice that the patch is patch 908, however if you look at the hudson page it's linked to the change is documented as 909 patch file applied
> https://hudson.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/25/changes
> I looked at both jiras ZOOKEEPER-908 and ZOOKEEPER-909 both of these look good (the right names on patches) and qabot actually updated 908 with the comment (failure). However the "change" is listed as 909 which is wrong.
>     [exec] -1 overall.  Here are the results of testing the latest attachment
>     [exec]   http://issues.apache.org/jira/secure/attachment/12459361/ZOOKEEPER-908.patch
>     [exec]   against trunk revision 1033770.
>     [exec]
>     [exec]     +1 @author.  The patch does not contain any @author tags.
>     [exec]
>     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified tests.
>     [exec]                         Please justify why no new tests are needed for this patch.
>     [exec]                         Also please list what manual steps were performed to verify this patch.
>     [exec]
>     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
>     [exec]
>     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
>     [exec]
>     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
>     [exec]
>     [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
>     [exec]
>     [exec]     +1 core tests.  The patch passed core unit tests.
>     [exec]
>     [exec]     +1 contrib tests.  The patch passed contrib unit tests.
>     [exec]
>     [exec] Test results: https://hudson.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/25//testReport/
>     [exec] Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/25//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
>     [exec] Console output: https://hudson.apache.org/hudson/job/PreCommit-ZOOKEEPER-Build/25//console
>     [exec]
>     [exec] This message is automatically generated.
>     [exec]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.