harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Popov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-4002) [jdktools][jpda] JDWP test org.apache.harmony.jpda.tests.jdwp.ThreadReference.OwnedMonitorsTest is ambigous
Date Wed, 30 May 2007 16:11:16 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ivan Popov updated HARMONY-4002:

    Attachment: jpda_exclude.patch

Second patch 'jpda_exclude.patch' is to add this test to exclude list for JPDA module due
to know bug.

> [jdktools][jpda] JDWP test org.apache.harmony.jpda.tests.jdwp.ThreadReference.OwnedMonitorsTest
is ambigous
> -----------------------------------------------------------------------------------------------------------
>                 Key: HARMONY-4002
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4002
>             Project: Harmony
>          Issue Type: Bug
>          Components: JDK
>         Environment: Windows, Linux, harmony-jdk-r542764
>            Reporter: Ivan Popov
>         Attachments: jdwp_test.patch, jpda_exclude.patch
> The following JDWP unit test is ambigous:
>   org.apache.harmony.jpda.tests.jdwp.ThreadReference.OwnedMonitorsTest
> This test gets owned monitors of a tested thread and checks that each monitor is owned
by the tested thread. However, it does not check that all expected monitors are returned and
pass even if no monitors are returned. The test usually fails because of incorrect data returned
by JVMTI function GetOwnedMonitorInfo() reported in HARMONY-3866, but sometimes it passes.
The test should be improved to check number of owned monitors. At least two monitors are owned
by tested thread: waitForFinish and waitForStart.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message