Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 11 Jan 2016 22:36:40 +0000 (UTC)
From: "Ariel Weisberg (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12826944.1430752478000.78180.1452551800360@Atlassian.JIRA>
In-Reply-To: <JIRA.12826944.1430752478000@Atlassian.JIRA>
References: <JIRA.12826944.1430752478000@Atlassian.JIRA>
 <JIRA.12826944.1430752478203@arcas>
Subject: [jira] [Updated] (CASSANDRA-9293) Unit tests should fail if any
 LEAK DETECTED errors are printed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-9293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ariel Weisberg updated CASSANDRA-9293:
--------------------------------------
    Reviewer:   (was: Ariel Weisberg)

> 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
>            Reporter: Benedict
>            Assignee: Sylvestor George
>              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)