You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Elena Semukhina (JIRA)" <ji...@apache.org> on 2007/01/31 14:52:05 UTC
[jira] Updated: (HARMONY-3101) [drlvm][smoke tests] smoke tests
gc.WeakReferenceTest and gc.PhantomReferenceTest fail in some environment
[ https://issues.apache.org/jira/browse/HARMONY-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elena Semukhina updated HARMONY-3101:
-------------------------------------
Attachment: H-3101_smoke_gc_tests.patch
I attached the patch for the tests. I ran the tests a fwe times and did not see any failures.
> [drlvm][smoke tests] smoke tests gc.WeakReferenceTest and gc.PhantomReferenceTest fail in some environment
> ----------------------------------------------------------------------------------------------------------
>
> Key: HARMONY-3101
> URL: https://issues.apache.org/jira/browse/HARMONY-3101
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Environment: Windows XP
> Reporter: Elena Semukhina
> Attachments: H-3101_smoke_gc_tests.patch
>
>
> gc.WeakReferenceTest and gc.PhantomReferenceTest fail intermittently on Windows XP.
> Investigation showed up that the tests invoke ReferenceQueue.poll() method to check that a reference is enqueued immediately after gc() call but the spec says that newly-cleared weak references can be enqueued a little bit later.
> It's reasonable to add some waiting to the tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.