Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AED3A11F89 for ; Tue, 8 Apr 2014 22:45:31 +0000 (UTC) Received: (qmail 12728 invoked by uid 500); 8 Apr 2014 22:45:24 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 12667 invoked by uid 500); 8 Apr 2014 22:45:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 12520 invoked by uid 99); 8 Apr 2014 22:45:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 22:45:19 +0000 Date: Tue, 8 Apr 2014 22:45:19 +0000 (UTC) From: "Jing Zhao (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-10473) TestCallQueueManager is still flaky MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-10473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963554#comment-13963554 ] Jing Zhao commented on HADOOP-10473: ------------------------------------ Two nits: # The following change will duplicate the comment: {code} + + // Ensure no calls were dropped {code} # We can remove the following change: {code} - } + } {code} Other than this +1. > TestCallQueueManager is still flaky > ----------------------------------- > > Key: HADOOP-10473 > URL: https://issues.apache.org/jira/browse/HADOOP-10473 > Project: Hadoop Common > Issue Type: Bug > Components: test > Reporter: Tsz Wo Nicholas Sze > Assignee: Tsz Wo Nicholas Sze > Priority: Minor > Attachments: c10473_20140408.patch > > > testSwapUnderContention counts the calls and then interrupts as shown below. There could be call after counting the call but before interrupt. > {code} > for (Taker t : consumers) { > totalCallsConsumed += t.callsTaken; > threads.get(t).interrupt(); > } > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)