[jbosstools-issues] [JBoss JIRA] (JBIDE-16419) JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests
Victor Rubezhny (JIRA)
issues at jboss.org
Tue Feb 4 04:14:30 EST 2014
[ https://issues.jboss.org/browse/JBIDE-16419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12940963#comment-12940963 ]
Victor Rubezhny edited comment on JBIDE-16419 at 2/4/14 4:13 AM:
-----------------------------------------------------------------
Doesn't look like a deadlock, but does look like a hang (infinite loop) in native code:
[Bug 354842 - Hang in org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842]
was (Author: vrubezhny):
Doesn't look like a deadlock, but do look like a hang in native code:
[Bug 354842 - Hang in org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)|https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842]
> JUnit Test failure: investigate time out/deadlock in JSF UI JUnit Tests
> -----------------------------------------------------------------------
>
> Key: JBIDE-16419
> URL: https://issues.jboss.org/browse/JBIDE-16419
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Alpha1
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Alpha2
>
> Attachments: jstack.27042.log
>
>
> Sometimes JUnit Tests for jbosstools-javaee component fail with timeout (probably deadlocked).
> See example stacktrace attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list