hudson qabot incorrectly reporting issues as number 909 when the patch from 908 
is the one being tested

                 Key: ZOOKEEPER-929
             Project: Zookeeper
          Issue Type: Bug
          Components: build
            Reporter: Patrick Hunt
            Assignee: Nigel Daley

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

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]   against trunk revision 1033770.
    [exec]     +1 @author.  The patch does not contain any @author tags.
    [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]     +1 javadoc.  The javadoc tool did not generate any warning 
    [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
    [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
    [exec]     +1 release audit.  The applied patch does not increase the total 
number of release audit warnings.
    [exec]     +1 core tests.  The patch passed core unit tests.
    [exec]     +1 contrib tests.  The patch passed contrib unit tests.
    [exec] Test results:
    [exec] Findbugs warnings:
    [exec] Console output:
    [exec] This message is automatically generated.

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

Reply via email to