Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <12882955.1165846464789.JavaMail.jira@brutus>
Date: Mon, 11 Dec 2006 06:14:24 -0800 (PST)
From: "weldon washburn (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-2343) [drlvm][kernel test]
 ThreadTest.testYield() fails intermittently on linux.
In-Reply-To: <5508739.1164713302473.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HARMONY-2343?page=all ]

weldon washburn closed HARMONY-2343.
------------------------------------

    Resolution: Duplicate

This bug was fixed when 2204 was committed.  Its a duplicate of 2204.

> [drlvm][kernel test] ThreadTest.testYield() fails intermittently on linux.
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-2343
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2343
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Elena Semukhina
>         Assigned To: weldon washburn
>         Attachments: H-2343_ThreadTest.patch, ThreadYield.java
>
>
> The ThreadTest.testYield() fails approximately once per 10 runs. It fails mainly in the batch mode and usually passes when running separately.
> The attached test is an excerpt from ThreadTest but it is not an issue reproducer. On the contrary, it demonstrates fine threads alternating on DRLVM while it always fails on RI 1.5.0_08. 
> Nevertheless, I think ThreadTest is not quite correct. The spec says:
> (yield) Causes the currently executing thread object to temporarily pause and allow other threads to execute.
> The test should not expect that the two threads alternate. Any other thread can execute while some thread yields. And this happens most likely when a lot of threads are alive during the test run.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira