This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[200406131800] It seems like xtest doesn't know how to kill IDE on Windows (XP or Win2K), JDS / Sol9 / Linux RH9 work fine. I've never deeply investigate it, just after long long long time (5-7 hours - my timeout = 1 hour) I look at Win machine and there is frozen IDE , if I list all processes there is one nbexec process , BUT there isn't netbeans process, I think that xtest kill "netbeans" process but nbexec isn't killed, so harness can't run next tests, because IDE is still opened... These days, when IDE (with refuc*toring) is near to untestable state and xtest can't kill IDE if "something happend", automated tests come to the half hands/automated mode !!!
First attempt on build 20040620-2224 was successful. IDE was killed after specified time. My environment is WindowXP, JDK1.4.2_04.
It works for me also on JDK1.5.0. Please, give a test case to reproduce.
It doesn't work as I said you today morning ;( I don't have separate test case, (with only one test case, short timeout, and separate infrastructure) , but every morning I see not killed nbexec process on both machines (XP+2K) and all infrastructure stays ......
Is this still a valid issue?
No feedback that there is still a problem with killing of IDE.
Ok, wait for next problematic build , when xtest has to kill IDE ;)