[
https://issues.apache.org/jira/browse/BOOKKEEPER-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13527359#comment-13527359
]
Hudson commented on BOOKKEEPER-474:
-----------------------------------
Integrated in bookkeeper-trunk #845 (See
[https://builds.apache.org/job/bookkeeper-trunk/845/])
BOOKKEEPER-474: BookieReadWriteTest#testShutdown doesn't make sense (ivank
via fpj) (Revision 1418685)
Result = SUCCESS
fpj :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/proto/TestPerChannelBookieClient.java
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/test/BookieReadWriteTest.java
> BookieReadWriteTest#testShutdown doesn't make sense
> ---------------------------------------------------
>
> Key: BOOKKEEPER-474
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-474
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments:
> 0001-Moved-testShutdown-out-of-BookieReadWriteTest-and-ma.patch,
> 0002-BOOKKEEPER-474-Remove-testShutdown-replace-with-more.patch,
> 0002-BOOKKEEPER-474-Remove-testShutdown-replace-with-more.patch
>
>
> This test was created to catch the BOOKKEEPER-5, which is where we hang due
> to orphaned netty connections. Netty connections are made when we first send
> an add entry to the bookie.
> The creates 10000 ledgers, and writes 200 entries to across these (note, this
> is not 200 each, but 200 across all ledgers). Therefore, a maximum 200
> connections could be created. So the test isn't doing what it think it is
> doing.
> The test takes between 4 & 7 minutes (most of this time creating unused
> ledgers) on jenkins. It is then run 4 times as BookieReadWriteTest is a
> Parameterized test.
> This adds up to 28 minutes to a build on jenkins. This test should take no
> longer than 30 seconds.
--
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
