[
https://issues.apache.org/jira/browse/BOOKKEEPER-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539415#comment-13539415
]
Flavio Junqueira commented on BOOKKEEPER-525:
---------------------------------------------
The way I see around this is to have a wait with a timeout instead of an
unconditional wait call, and fail if too many wait calls time out. Perhaps this
is what you have in mind but it is not clear from your description. Another way
is to rely upon what Ivan has proposed here: BOOKKEEPER-523.
> Should not using Junit Assert in CallBack method in BK test.
> ------------------------------------------------------------
>
> Key: BOOKKEEPER-525
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-525
> Project: Bookkeeper
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: Han Xiao
>
> There are many jiras to solve the problem of running forever of bk test.
> Many of them are coming from the using 'Junit Assert' in callback. The using
> must be revised through the entire test project.
--
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
