[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797304#action_12797304
 ] 

Hadoop QA commented on ZOOKEEPER-637:
-------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12429574/ZOOKEEPER-632_2.patch
  against trunk revision 896551.

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

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/31/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/31/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h7.grid.sp2.yahoo.net/31/console

This message is automatically generated.

> Trunk build is failing
> ----------------------
>
>                 Key: ZOOKEEPER-637
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-637
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: build
>            Reporter: Flavio Paiva Junqueira
>            Assignee: Flavio Paiva Junqueira
>         Attachments: ZOOKEEPER-632_2.patch, ZOOKEEPER-637.patch
>
>
> The trunk build is failing when Hudson runs it. The problem seems to be that 
> ivy-init is executed only once, but its definitions (in particular 
> ivy:settings) do not persist, and the failure occurs when we run ivy-retrieve 
> a second time, which requires the definition of ivy:settings.
> It seems that the problem occur with ant 1.7.0, but not with 1.7.1, so it 
> could be an ant issue. 

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