[
https://issues.apache.org/jira/browse/CASSANDRA-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579703#comment-14579703
]
Ariel Weisberg commented on CASSANDRA-9293:
-------------------------------------------
The leak detection code is loaded into every test that might leak. So you have
a hook to inject behavior and it's already generating output you can use to
drive test pass/failure.
My suggestion is to modify the junit formatters so that they mark test classes
with leaks as failures, or maybe append a fake test that just indicates the
test class has leaks.
> Unit tests should fail if any LEAK DETECTED errors are printed
> --------------------------------------------------------------
>
> Key: CASSANDRA-9293
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9293
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Philip Thompson
> Labels: test
> Attachments: 9293.txt
>
>
> We shouldn't depend on dtests to inform us of these problems (which have
> error log monitoring) - they should be caught by unit tests, which may also
> cover different failure conditions (besides being faster).
> There are a couple of ways we could do this, but probably the easiest is to
> add a static flag that is set to true if we ever see a leak (in Ref), and to
> just assert that this is false at the end of every test.
> [~enigmacurry] is this something TE can help with?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
