FEST

Deadlock when running TestNG with multiple threads (issue 122)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: FEST-Swing 1.1
  • Fix Version/s: FEST-Swing 1.2rc
  • Component/s: Swing
  • Labels:
    None
  • Number of attachments :
    0

Description

From Dan Dyer:

What steps will reproduce the problem?
1. In testng.xml, set parallel="tests" and threadcount="2".
2. Create test cases in 2 separate tests that use FEST Swing.

What is the expected output? What do you see instead?
Should work fine.

What version of the product are you using? On what operating system?
There is a deadlock that prevents the test run from completing. Seemingly related to the ScreenLock class.

Please provide any additional information below.
Using TestNG from Ant on Windows XP with JDK 1.5.0_10.


Original report: Issue 122 (Google Code)

Activity

Hide
Martin Bachmann added a comment -

Send the blocked VM process signal 3. Then the VM will show you any obvious deadlocks. Under Linux it's "kill -3 <pid>", under Windows Ctrl-Break or this tool (http://www.latenighthacking.com/projects/2003/sendSignal/) will do the trick. Maybe it helps to track that down.

Show
Martin Bachmann added a comment - Send the blocked VM process signal 3. Then the VM will show you any obvious deadlocks. Under Linux it's "kill -3 <pid>", under Windows Ctrl-Break or this tool (http://www.latenighthacking.com/projects/2003/sendSignal/) will do the trick. Maybe it helps to track that down.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: