From dev-return-63615-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Mon Jan 22 17:52:44 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 86230180609 for ; Mon, 22 Jan 2018 17:52:44 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 74235160C4B; Mon, 22 Jan 2018 16:52:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B2477160C3A for ; Mon, 22 Jan 2018 17:52:43 +0100 (CET) Received: (qmail 61238 invoked by uid 500); 22 Jan 2018 16:52:42 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 61224 invoked by uid 99); 22 Jan 2018 16:52:42 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jan 2018 16:52:42 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id BF60CE110A; Mon, 22 Jan 2018 16:52:40 +0000 (UTC) From: clebertsuconic To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis issue #1800: ARTEMIS-1626 Disable thread leak check for fai... Content-Type: text/plain Message-Id: <20180122165240.BF60CE110A@git1-us-west.apache.org> Date: Mon, 22 Jan 2018 16:52:40 +0000 (UTC) Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1800 @gaohoward the idea world is far from reality.. there are tests that will be failing forever on the testsuite and people will ignore them.. a result will be a mess that people won't know where the leaks are coming from again. The ThreadLeak Rule has prevented leaked threads to fail non related tests.. and the threadleak rule is not only logging, but it's also trying to interrupt these leaked threads... Lets not regress on that please! We can do a faster check (not wait for a whole minute on failted tests.. and we would only logg. instead of fail).. it's a simple change. ---