[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534652#comment-13534652
 ] 

Hadoop QA commented on BOOKKEEPER-509:
--------------------------------------

Testing JIRA BOOKKEEPER-509


Patch 
[BOOKKEEPER-509.diff|https://issues.apache.org/jira/secure/attachment/12561424/BOOKKEEPER-509.diff]
 downloaded at Tue Dec 18 05:01:27 UTC 2012

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:red}-1{color} the patch contains 1 line(s) with trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
120
.    {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 FINDBUGS{color}
.    {color:green}+1{color} the patch does not seem to introduce new Findbugs 
warnings
{color:green}+1 TESTS{color}
.    Tests run: 499
{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/139/
                
> TestBookKeeperPersistenceManager failed on latest trunk
> -------------------------------------------------------
>
>                 Key: BOOKKEEPER-509
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-509
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-509.diff, BOOKKEEPER-509.diff, 
> BOOKKEEPER-509.diff, BOOKKEEPER-509.diff, hedwig-server.log, 
> hedwig-server.log.bak
>
>
> latest trunk failed at TestBookKeeperPersistenceManager.
> sees that it caused by uncaught exception:
> {code}
> java.util.NoSuchElementException
>         at java.util.AbstractQueue.remove(AbstractQueue.java:90)
>         at 
> org.apache.bookkeeper.client.PendingReadOp.nextElement(PendingReadOp.java:345)
>         at 
> org.apache.bookkeeper.client.PendingReadOp.nextElement(PendingReadOp.java:53)
>         at 
> org.apache.bookkeeper.client.LedgerRecoveryOp.readComplete(LedgerRecoveryOp.java:100)
>         at 
> org.apache.bookkeeper.client.PendingReadOp.submitCallback(PendingReadOp.java:338)
>         at 
> org.apache.bookkeeper.client.PendingReadOp.readEntryComplete(PendingReadOp.java:327)
>         at 
> org.apache.bookkeeper.proto.PerChannelBookieClient.handleReadResponse(PerChannelBookieClient.java:627)
>         at 
> org.apache.bookkeeper.proto.PerChannelBookieClient$7.safeRun(PerChannelBookieClient.java:529)
>         at org.apache.bookkeeper.util.SafeRunnable.run(SafeRunnable.java:31)
>         at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>         at java.lang.Thread.run(Thread.java:680)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to