On Wed, 24 Apr 2024 00:01:45 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
On Wed, 24 Apr 2024 00:01:45 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> same approach is used for `EnteringTask` threads. It has been
On Tue, 23 Apr 2024 20:47:34 GMT, Chris Plummer wrote:
>> Serguei Spitsyn has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> review: tweak in wait_for_state func to allow exp_state bit mask
>
>
On Thu, 18 Apr 2024 21:56:09 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
On Thu, 18 Apr 2024 21:56:09 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> same approach is used for `EnteringTask` threads. It has been
On Tue, 16 Apr 2024 21:55:54 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
On Tue, 16 Apr 2024 21:55:54 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> same approach is used for `EnteringTask` threads. It has been
On Tue, 16 Apr 2024 19:21:16 GMT, Leonid Mesnik wrote:
> The fix looks good, just one nit. rml.wait(100); might be changed to plain
> sleep(100)
Right, thanks. Will fix it.
-
PR Comment: https://git.openjdk.org/jdk/pull/18778#issuecomment-2059950982
On Tue, 16 Apr 2024 06:08:58 GMT, Serguei Spitsyn wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
>> event but has not released the `lockCheck` monitor yet. It has been fixed to
>> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
> same approach is used for `EnteringTask` threads. It has been
On Mon, 15 Apr 2024 21:34:48 GMT, Leonid Mesnik wrote:
>> Serguei Spitsyn has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> review: removed event_lock; moved wait_for_state() to jvmti_common.hpp
>
>
On Mon, 15 Apr 2024 06:47:24 GMT, Serguei Spitsyn wrote:
> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait`
> event but has not released the `lockCheck` monitor yet. It has been fixed to
> wait for each `WaitingTask` thread to really reach the `WAITING` state. The
>
This is the test issue. The `WaitingPT3` thread posted the `MonitorWait` event
but has not released the `lockCheck` monitor yet. It has been fixed to wait for
each `WaitingTask` thread to really reach the `WAITING` state. The same
approach is used for `EnteringTask` threads. It has been fixed
16 matches
Mail list logo
