Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 3 Aug 2015 15:35:04 +0000 (UTC)
From: "Benedict (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12851130.1438616053000.355913.1438616104521@Atlassian.JIRA>
In-Reply-To: <JIRA.12851130.1438616053000@Atlassian.JIRA>
References: <JIRA.12851130.1438616053000@Atlassian.JIRA>
 <JIRA.12851130.1438616053033@arcas>
Subject: [jira] [Created] (CASSANDRA-9962) WaitQueueTest is flakey
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Benedict created CASSANDRA-9962:
-----------------------------------

             Summary: WaitQueueTest is flakey
                 Key: CASSANDRA-9962
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9962
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Benedict
            Assignee: Benedict
            Priority: Minor
             Fix For: 3.x


While the test is a little noddy, and superfluous, it shouldn't fail even vanishingly infrequently. [~aweisberg] has spotted it doing so, and I have also encountered it once, so I suspect that a change in hardware/OS may have made vanishingly unlikely just pretty unlikely, which is even less good. 

Right now it depends on {{Thread.start()}} completing before the new thread starts; this isn't guaranteed. This patch fixes that.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)