From dev-return-63662-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Tue Jan 23 03:25:04 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 E3FB2180609 for ; Tue, 23 Jan 2018 03:25:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D47C3160C4C; Tue, 23 Jan 2018 02:25:04 +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 26FC7160C4B for ; Tue, 23 Jan 2018 03:25:04 +0100 (CET) Received: (qmail 10609 invoked by uid 500); 23 Jan 2018 02:25:03 -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 10433 invoked by uid 99); 23 Jan 2018 02:25:02 -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; Tue, 23 Jan 2018 02:25:02 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 51028F3551; Tue, 23 Jan 2018 02:25:02 +0000 (UTC) From: gaohoward To: dev@activemq.apache.org Reply-To: dev@activemq.apache.org References: In-Reply-To: Subject: [GitHub] activemq-artemis pull request #1800: ARTEMIS-1626 Disable thread leak check ... Content-Type: text/plain Message-Id: <20180123022502.51028F3551@git1-us-west.apache.org> Date: Tue, 23 Jan 2018 02:25:02 +0000 (UTC) GitHub user gaohoward reopened a pull request: https://github.com/apache/activemq-artemis/pull/1800 ARTEMIS-1626 Disable thread leak check for failing tests The ThreadLeakCheckRule is used to check thread leaks after each test is finished. However when a test fails, it is not necessary to check leaking threads because the test failure should be fixed anyway. And leaking threads in a failed test may well be a result of the failure (once the test is fixed the thread leak may be gone). If a failed test also leaks threads, it takes a long time before the thread leak check finishes (60 seconds checking time), thus it takes a long time to finish, especially when tests are run in batches with failures. So to improve this, it should be reasonable to just enable the thread leaking check for each test passes, and disable the check when a test fails. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gaohoward/activemq-artemis fthread_rule Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/1800.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1800 ---- commit c8e25c72b9885bb08ec9dd5d8502c273b349d46a Author: Howard Gao Date: 2018-01-22T14:39:23Z ARTEMIS-1626 Disable thread leak check for failing tests The ThreadLeakCheckRule is used to check thread leaks after each test is finished. However when a test fails, it is not necessary to check leaking threads because the test failure should be fixed anyway. And leaking threads in a failed test may well be a result of the failure (once the test is fixed the thread leak may be gone). If a failed test also leaks threads, it takes a long time before the thread leak check finishes (60 seconds checking time), thus it takes a long time to finish, especially when tests are run in batches with failures. So to improve this, it should be reasonable to just enable the thread leaking check for each test passes, and disable the check when a test fails. ---- ---