You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/12/28 14:45:55 UTC
[jira] Commented: (HARMONY-4232) [testing][reliablity]
ThreadKillTest hangs
[ https://issues.apache.org/jira/browse/HARMONY-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554760 ]
Vladimir Beliaev commented on HARMONY-4232:
-------------------------------------------
It looks like the right way to name this JIRA is [buildtes][reliability] - please get this fixed. This will allow to use the filters correctly.
> [testing][reliablity] ThreadKillTest hangs
> ------------------------------------------
>
> Key: HARMONY-4232
> URL: https://issues.apache.org/jira/browse/HARMONY-4232
> Project: Harmony
> Issue Type: Bug
> Components: build - test - ci
> Environment: Win
> Reporter: Aleksey Ignatenko
>
> Reliability test api.kernel.thread.ThreadKill.ThreadKillTest hangs running on drlvm both on release and debug binaries.
> I watch the deadlock with the debugger and saw that several monitors are waiting on "Object" object. I suppose it could be public static Object lock = new Object(); in the test.
> Trying to localize the issue I found that:
> - t[k].join(); does not affect test hanging
> - king of threads does not affect test hanging (not matter MathThread or IOThread).
> Vera Petrashkova also reported that test hangs sometimes on RI. Therefore I mark it as [testing][reliablity] for now but not [drlvm][threadding].
> Need additional investigation by threadding gurus.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.