You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vera Petrashkova (JIRA)" <ji...@apache.org> on 2007/07/03 08:53:04 UTC

[jira] Created: (HARMONY-4314) [buildtest][vts] Some vm/jvmti tests incorrectly use Thread.sleep() for synchronization

[buildtest][vts] Some vm/jvmti tests incorrectly use Thread.sleep() for synchronization
---------------------------------------------------------------------------------------

                 Key: HARMONY-4314
                 URL: https://issues.apache.org/jira/browse/HARMONY-4314
             Project: Harmony
          Issue Type: Bug
          Components: build - test - ci
            Reporter: Vera Petrashkova
            Priority: Minor


The following VTS JVMTI tests create some threads and incorrectly use Thread.sleep() to synchronize their execution.
As the result these tests intermittently fail.


vm/jvmti/events /MonitorContendedEntered/MonitorContendedEntered0101
vm/jvmti/events /MonitorContendedEntered/MonitorContendedEntered0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0101
vm/jvmti/funcs/GetAllThreads/GetAllThreads0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0103
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0101
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0101
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0103
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0104
vm/jvmti/funcs/GetOwnedMonitorInfo/GetOwnedMonitorInfo0101
vm/jvmti/funcs/GetThreadGroupChildren/GetThreadGroupChildren0101
vm/jvmti/funcs/GetThreadGroupInfo/GetThreadGroupInfo0101
vm/jvmti/funcs/InterruptThreaD/InterruptThread0101
vm/jvmti/funcs/PopFrame/PopFrame0101
vm/jvmti/funcs/PopFrame/PopFrame0102
vm/jvmti/funcs/PopFrame/PopFrame0104
vm/jvmti/funcs/PopFrame/PopFrame0105
vm/jvmti/funcs/PopFrame/PopFrame0106
vm/jvmti/funcs/PopFrame/PopFrame0107
vm/jvmti/funcs/ResumeThread/ResumeThread0101
vm/jvmti/funcs/ResumeThread/ResumeThread0102
vm/jvmti/funcs/ResumeThread/ResumeThread0103
vm/jvmti/funcs/ResumeThread/ResumeThread0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0101
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0102
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0103
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0105
vm/jvmti/funcs/StopThread/StopThread0101
vm/jvmti/funcs/StopThread/StopThread0102
vm/jvmti/funcs/StopThread/StopThread0103
vm/jvmti/funcs/StopThread/StopThread0104
vm/jvmti/funcs/StopThread/StopThread0105
vm/jvmti/funcs/SuspendThread/SuspendThread0101
vm/jvmti/funcs/SuspendThread/SuspendThread0102
vm/jvmti/funcs/SuspendThread/SuspendThread0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0101
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0102
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0104
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0105

For example, 
vm/jvmti/funcs/ResumeThread/ResumeThread0103 expects that VM returns code 
JVMTI_ERROR_THREAD_NOT_SUSPENDED(13) but VM returns JVMTI_ERROR_THREAD_NOT_ALIVE (15) 
because created thread was already died and this test fails.





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


[jira] Updated: (HARMONY-4314) [buildtest][vts] Some vm/jvmti tests incorrectly use Thread.sleep() for synchronization

Posted by "Vera Petrashkova (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vera Petrashkova updated HARMONY-4314:
--------------------------------------

    Description: 
The following VTS JVMTI tests create some threads and incorrectly use Thread.sleep() to synchronize their execution.
As the result these tests intermittently fail.


vm/jvmti/events/MonitorContendedEntered/MonitorContendedEntered0101
vm/jvmti/events/MonitorContendedEntered/MonitorContendedEntered0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0101
vm/jvmti/funcs/GetAllThreads/GetAllThreads0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0103
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0101
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0101
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0103
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0104
vm/jvmti/funcs/GetOwnedMonitorInfo/GetOwnedMonitorInfo0101
vm/jvmti/funcs/GetThreadGroupChildren/GetThreadGroupChildren0101
vm/jvmti/funcs/GetThreadGroupInfo/GetThreadGroupInfo0101
vm/jvmti/funcs/InterruptThreaD/InterruptThread0101
vm/jvmti/funcs/PopFrame/PopFrame0101
vm/jvmti/funcs/PopFrame/PopFrame0102
vm/jvmti/funcs/PopFrame/PopFrame0104
vm/jvmti/funcs/PopFrame/PopFrame0105
vm/jvmti/funcs/PopFrame/PopFrame0106
vm/jvmti/funcs/PopFrame/PopFrame0107
vm/jvmti/funcs/ResumeThread/ResumeThread0101
vm/jvmti/funcs/ResumeThread/ResumeThread0102
vm/jvmti/funcs/ResumeThread/ResumeThread0103
vm/jvmti/funcs/ResumeThread/ResumeThread0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0101
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0102
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0103
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0105
vm/jvmti/funcs/StopThread/StopThread0101
vm/jvmti/funcs/StopThread/StopThread0102
vm/jvmti/funcs/StopThread/StopThread0103
vm/jvmti/funcs/StopThread/StopThread0104
vm/jvmti/funcs/StopThread/StopThread0105
vm/jvmti/funcs/SuspendThread/SuspendThread0101
vm/jvmti/funcs/SuspendThread/SuspendThread0102
vm/jvmti/funcs/SuspendThread/SuspendThread0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0101
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0102
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0104
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0105

For example, 
vm/jvmti/funcs/ResumeThread/ResumeThread0103 expects that VM returns code 
JVMTI_ERROR_THREAD_NOT_SUSPENDED(13) but VM returns JVMTI_ERROR_THREAD_NOT_ALIVE (15) 
because created thread was already died and this test fails.





  was:
The following VTS JVMTI tests create some threads and incorrectly use Thread.sleep() to synchronize their execution.
As the result these tests intermittently fail.


vm/jvmti/events /MonitorContendedEntered/MonitorContendedEntered0101
vm/jvmti/events /MonitorContendedEntered/MonitorContendedEntered0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0101
vm/jvmti/funcs/GetAllThreads/GetAllThreads0102
vm/jvmti/funcs/GetAllThreads/GetAllThreads0103
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0101
vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0101
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0102
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0103
vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0104
vm/jvmti/funcs/GetOwnedMonitorInfo/GetOwnedMonitorInfo0101
vm/jvmti/funcs/GetThreadGroupChildren/GetThreadGroupChildren0101
vm/jvmti/funcs/GetThreadGroupInfo/GetThreadGroupInfo0101
vm/jvmti/funcs/InterruptThreaD/InterruptThread0101
vm/jvmti/funcs/PopFrame/PopFrame0101
vm/jvmti/funcs/PopFrame/PopFrame0102
vm/jvmti/funcs/PopFrame/PopFrame0104
vm/jvmti/funcs/PopFrame/PopFrame0105
vm/jvmti/funcs/PopFrame/PopFrame0106
vm/jvmti/funcs/PopFrame/PopFrame0107
vm/jvmti/funcs/ResumeThread/ResumeThread0101
vm/jvmti/funcs/ResumeThread/ResumeThread0102
vm/jvmti/funcs/ResumeThread/ResumeThread0103
vm/jvmti/funcs/ResumeThread/ResumeThread0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0101
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0102
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0103
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0104
vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0105
vm/jvmti/funcs/StopThread/StopThread0101
vm/jvmti/funcs/StopThread/StopThread0102
vm/jvmti/funcs/StopThread/StopThread0103
vm/jvmti/funcs/StopThread/StopThread0104
vm/jvmti/funcs/StopThread/StopThread0105
vm/jvmti/funcs/SuspendThread/SuspendThread0101
vm/jvmti/funcs/SuspendThread/SuspendThread0102
vm/jvmti/funcs/SuspendThread/SuspendThread0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0101
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0102
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0103
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0104
vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0105

For example, 
vm/jvmti/funcs/ResumeThread/ResumeThread0103 expects that VM returns code 
JVMTI_ERROR_THREAD_NOT_SUSPENDED(13) but VM returns JVMTI_ERROR_THREAD_NOT_ALIVE (15) 
because created thread was already died and this test fails.






> [buildtest][vts] Some vm/jvmti tests incorrectly use Thread.sleep() for synchronization
> ---------------------------------------------------------------------------------------
>
>                 Key: HARMONY-4314
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4314
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>            Reporter: Vera Petrashkova
>            Priority: Minor
>
> The following VTS JVMTI tests create some threads and incorrectly use Thread.sleep() to synchronize their execution.
> As the result these tests intermittently fail.
> vm/jvmti/events/MonitorContendedEntered/MonitorContendedEntered0101
> vm/jvmti/events/MonitorContendedEntered/MonitorContendedEntered0102
> vm/jvmti/funcs/GetAllThreads/GetAllThreads0101
> vm/jvmti/funcs/GetAllThreads/GetAllThreads0102
> vm/jvmti/funcs/GetAllThreads/GetAllThreads0103
> vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0101
> vm/jvmti/funcs/GetCurrentContendedMonitor/GetCurrentContendedMonitor0102
> vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0101
> vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0102
> vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0103
> vm/jvmti/funcs/GetObjectMonitorUsage/GetObjectMonitorUsage0104
> vm/jvmti/funcs/GetOwnedMonitorInfo/GetOwnedMonitorInfo0101
> vm/jvmti/funcs/GetThreadGroupChildren/GetThreadGroupChildren0101
> vm/jvmti/funcs/GetThreadGroupInfo/GetThreadGroupInfo0101
> vm/jvmti/funcs/InterruptThreaD/InterruptThread0101
> vm/jvmti/funcs/PopFrame/PopFrame0101
> vm/jvmti/funcs/PopFrame/PopFrame0102
> vm/jvmti/funcs/PopFrame/PopFrame0104
> vm/jvmti/funcs/PopFrame/PopFrame0105
> vm/jvmti/funcs/PopFrame/PopFrame0106
> vm/jvmti/funcs/PopFrame/PopFrame0107
> vm/jvmti/funcs/ResumeThread/ResumeThread0101
> vm/jvmti/funcs/ResumeThread/ResumeThread0102
> vm/jvmti/funcs/ResumeThread/ResumeThread0103
> vm/jvmti/funcs/ResumeThread/ResumeThread0104
> vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0101
> vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0102
> vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0103
> vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0104
> vm/jvmti/funcs/ResumeThreadList/ResumeThreadList0105
> vm/jvmti/funcs/StopThread/StopThread0101
> vm/jvmti/funcs/StopThread/StopThread0102
> vm/jvmti/funcs/StopThread/StopThread0103
> vm/jvmti/funcs/StopThread/StopThread0104
> vm/jvmti/funcs/StopThread/StopThread0105
> vm/jvmti/funcs/SuspendThread/SuspendThread0101
> vm/jvmti/funcs/SuspendThread/SuspendThread0102
> vm/jvmti/funcs/SuspendThread/SuspendThread0103
> vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0101
> vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0102
> vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0103
> vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0104
> vm/jvmti/funcs/SuspendThreadList/SuspendThreadList0105
> For example, 
> vm/jvmti/funcs/ResumeThread/ResumeThread0103 expects that VM returns code 
> JVMTI_ERROR_THREAD_NOT_SUSPENDED(13) but VM returns JVMTI_ERROR_THREAD_NOT_ALIVE (15) 
> because created thread was already died and this test fails.

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