Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BD0098A6 for ; Fri, 22 Feb 2013 18:18:13 +0000 (UTC) Received: (qmail 4854 invoked by uid 500); 22 Feb 2013 18:18:12 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 4799 invoked by uid 500); 22 Feb 2013 18:18:12 -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 4542 invoked by uid 99); 22 Feb 2013 18:18:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Feb 2013 18:18:12 +0000 Date: Fri, 22 Feb 2013 18:18:12 +0000 (UTC) From: "Kevin Earls (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQ-4342) MemoryUsageCleanupTest fails intermittently MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Kevin Earls created AMQ-4342: -------------------------------- Summary: MemoryUsageCleanupTest fails intermittently Key: AMQ-4342 URL: https://issues.apache.org/jira/browse/AMQ-4342 Project: ActiveMQ Issue Type: Bug Components: Test Cases Reporter: Kevin Earls Priority: Minor This test fails intermittently at a point where it expects BrokerView.getMemoryPercentUsage() to return 0, but it returns 1. The problem here is that getMemoryPercentageUsage returns an int, and that number is truncated when calculated. I did some debugging and found when the test fails the actual usage is about 0.85%, and when it fails it's only 1.02%. I'll attach a patch that makes the assertion here slightly more lenient to accommodate for this. -- 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