[
https://issues.apache.org/jira/browse/BOOKKEEPER-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-533:
----------------------------------
Attachment: 0001-BOOKKEEPER-533-TestSubAfterCloseSub-fails-strangely-.patch
This one has it.
> TestSubAfterCloseSub fails strangely in tests
> ---------------------------------------------
>
> Key: BOOKKEEPER-533
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-533
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Ivan Kelly
> Fix For: 4.2.0
>
> Attachments:
> 0001-BOOKKEEPER-533-TestSubAfterCloseSub-fails-strangely-.patch,
> 0001-BOOKKEEPER-533-TestSubAfterCloseSub-fails-strangely-.patch,
> 0001-BOOKKEEPER-533-TestSubAfterCloseSub-fails-strangely-.patch,
> BOOKKEEPER-513.diff, BOOKKEEPER-513.diff, BOOKKEEPER-533.diff,
> BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, BOOKKEEPER-533.diff,
> BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, BOOKKEEPER-533.diff,
> BOOKKEEPER-533.diff, BOOKKEEPER-533.diff, hedwig-server.log, stack.txt
>
>
> Example https://builds.apache.org/job/bookkeeper-trunk-precommit-build/204/
> It looks like the maven surefire process exits, as if System.exit() is being
> called. This should be the case since BOOKKEEPER-522, which removes all calls
> to System.exit()
--
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
