[
https://issues.apache.org/jira/browse/BOOKKEEPER-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13529727#comment-13529727
]
Hudson commented on BOOKKEEPER-497:
-----------------------------------
Integrated in bookkeeper-trunk #855 (See
[https://builds.apache.org/job/bookkeeper-trunk/855/])
BOOKKEEPER-497: GcLedgersTest has a potential race (ivank via sijie)
(Revision 1420532)
Result = UNSTABLE
sijie :
Files :
* /zookeeper/bookkeeper/trunk/CHANGES.txt
*
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/meta/GcLedgersTest.java
> GcLedgersTest has a potential race
> ----------------------------------
>
> Key: BOOKKEEPER-497
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-497
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-497-GcLedgersTest-has-a-potential-race.patch
>
>
> The callbacks use Object#wait/notify without checking a condition. If the
> callback completes very quickly, the notify will happen before wait is ever
> called. The best solution is to use a CountDownLatch. Im seeing this problem
> when applying patch for BOOKKEEPER-205, probably due to a change in timing on
> the test.
--
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
