[ https://issues.jboss.org/browse/JBIDE-18818?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-18818 at 12/5/14 2:56 AM: ----------------------------------------------------------------- I noticed that actually in all javaee test timeouts o.j.t.jsf.ui.test killed first but despite of that sometimes jsf.verification.test is started anyway and killed too. Both jsf.ui and verification tests pass when I run them locally on my machine (mvn clean install ...) but I tend to blame *Display.getCurrent().readAndDispatch()* method which we use wildly in our tests and which may cause a deadlock and sometimes I see it when running locally too. I have no idea how we can fix this problem w/o removing a majority of our UI tests :( But again, if jenkins could provide a stack trace before killing the job it would be very useful to spot the problematic code in our tests. Can we run a script in parallel with jenkins build and run jstack or any other tool which can provide a stack trace of the jvm process just before the timeout is reached? The idea is to get a stack trace of the jvm process which is about to killed by timeout. Console output and Eclipse/Surefire logs are not very useful here. [~nickboldt], [~mickael_istria], [~dgolovin], WDYT? was (Author: akazakov): I noticed that actually in all javaee test timeouts o.j.t.jsf.ui.test killed first but despite of that sometimes jsf.verification.test is started anyway and killed too. Both jsf.ui and verification tests pass when I run them locally on my machine (mvn clean install ...) but I tend to blame Display.getCurrent().readAndDispatch() method which we use wildly in our tests and which may cause a deadlock and sometimes I see it when running locally too. I have no idea how we can fix this problem w/o removing a majority of our UI tests :( But again, if jenkins could provide a stack trace before killing the job it would be very useful to spot the problematic code in our tests. Can we run a script in parallel with jenkins build and run jstack or any other tool which can provide a stack trace of the jvm process just before the timeout is reached? The idea is to get a stack trace of the jvm process which is about to killed by timeout. Console output and Eclipse/Surefire logs are not very useful here. [~nickboldt], [~mickael_istria], [~dgolovin], WDYT? -- This message was sent by Atlassian JIRA (v6.3.8#6338)