You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2006/11/24 12:38:03 UTC
[jira] Assigned: (HARMONY-2294) [drlvm][kernel test] ObjectTest
needs to be included back to test runs
[ http://issues.apache.org/jira/browse/HARMONY-2294?page=all ]
Alexey Varlamov reassigned HARMONY-2294:
----------------------------------------
Assignee: Alexey Varlamov
> [drlvm][kernel test] ObjectTest needs to be included back to test runs
> ----------------------------------------------------------------------
>
> Key: HARMONY-2294
> URL: http://issues.apache.org/jira/browse/HARMONY-2294
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Elena Semukhina
> Assigned To: Alexey Varlamov
> Attachments: ObjectTest_fix.patch
>
>
> ObjectTest has been excluded from test runs some time ago. It occasionally failed on Windows on testWaitlongint() and testWait1() .
> I ran this test iteratively on drlvm and RI and found out that it failed on both VMs in the same way and with appoximately equal frequency.
> I fixed the test so that it passes on RI. The test passes on DRLVM too now.
> 1) testWaitlongint(): When failed, it always reported that it waited 499 ms instead of 500. I allowed the test to accept 1 ms less waiting time.
> 2) testWait1(): it reported that InterruptedException has not been thrown while the waiting thread was interrupted. Actually it failed very rarely (once per 1000 runs). I think this happens because the test does not correctly wait for the thread's run() method start. Fixed.
> 3) I added a minor fix to thread_native_condvar.c so that nanoseconds are rounded up rather than down.
> I ran the test iteratively on linux / Win XP / Win 2003 / jet, opt, int and have not seen a failure for a long time. The record is 4000 runs on Win 2003 / jet.
> I think the test should be included back to test runs.
--
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