robmayhew / fest

Automatically exported from code.google.com/p/fest
0 stars 0 forks source link

Deadlock when running TestNG with multiple threads #122

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
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 issue reported on code.google.com by british...@gmail.com on 29 Mar 2008 at 12:41

GoogleCodeExporter commented 9 years ago
FEST tests are executed in a serial manner on purpose. The reason being is that 
there
is only one mouse and one keyboard per computer that cannot be shared 
simultaneously
between two or more tests (e.g. both tests have their own dialogs and they need 
to
move the mouse or enter text at the same time.)

I'm going to mark this bug as a "invalid issue". Please feel free to change its
status to "new" if you consider something else can be done.

Original comment by Alex.Rui...@gmail.com on 29 Mar 2008 at 1:52

GoogleCodeExporter commented 9 years ago
Maybe I am misunderstanding, but I thought the purpose of the screen lock was 
to 
queue the tests and make them run in series, even if they are on different 
threads.

In other words, the second test is forced to wait until the first test 
completes, 
and then the second test can acquire the lock and run.

This is not what is happening.  One of the tests runs but the other does not.  
The 
entire Ant build deadlocks and the process has to be killed.  I am assuming 
that the 
first test is not properly releasing the lock.  When is the lock supposed to be 
released?  When cleanUp() is called?

Original comment by british...@gmail.com on 29 Mar 2008 at 2:04

GoogleCodeExporter commented 9 years ago
Hi Dan,

The screen lock is released when cleanUp(). I'm going to reopen this bug and 
investigate further, reproducing the scenario you described.

Thanks,
-Yvonne

Original comment by wanghy1...@gmail.com on 31 Mar 2008 at 2:51

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Issue migrated to http://jira.codehaus.org/browse/FEST-23

Original comment by Alex.Rui...@gmail.com on 2 Mar 2009 at 7:58