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.
I guess I found reproducible scanario for issue 77616 : The hint is to change Xtest property in one of your Test Run and push Start button : - tests are not running - machines can't be killed/diagnosed - server page is so slowwwwwww
Well, it looks like it's the exact behaviour as it was reported in issue 77616, scheduled tests should have started few minutes ago, but they didn't ;(
Thread-dump from one of the server : Jun 13, 2006 8:09:26 AM org.netbeans.test4u.system.process.ProcessExecutor run FINE: running df -k . in /space/test4u2 Exception in thread "Request dispatcher TCPServer" java.lang.ClassCastException: org.netbeans.test4u.tests.config.ConfigModule at org.ehucka.core.users.ParticipantCredential.accept(ParticipantCredential.java:56) at org.ehucka.core.servers.Server.accept(Server.java:152) at org.ehucka.core.api.task.TaskServer.canReceiveRequest(TaskServer.java:283) at org.ehucka.core.api.request.RequestServer.receiveRequest(RequestServer.java:52) at org.ehucka.core.api.task.TaskServer.addTask(TaskServer.java:94) at org.ehucka.core.api.task.TaskServer.responseRequest(TaskServer.java:278) at org.ehucka.core.api.request.RequestServer$DispatchThread.run(RequestServer.java:155) Jun 13, 2006 8:10:26 AM org.netbeans.test4u.system.task.DeleteBuildsTask perform FINE: 0 items removed.
Tests on the machines finish by: java.lang.IllegalArgumentException: Unexisting path key: temp.dir at org.ehucka.core.PathsConfiguration.getFile(PathsConfiguration.java:78) at org.netbeans.test4u.plugin.BuildArchive.install(BuildArchive.java:103) at org.netbeans.test4u.tests.request.TestRequestProcessor.processInstallBuild(TestRequestProcessor.java:131) at org.netbeans.test4u.tests.request.TestRequestProcessor.doProcessRequest(TestRequestProcessor.java:92) at org.netbeans.test4u.tests.request.TestRequestProcessor.responseRequest(TestRequestProcessor.java:54) at org.ehucka.core.api.request.RequestServer$DispatchThread.run(RequestServer.java:155)
Emane, what is the status of this issue ?
Fixed, there was a problem with 'too clever' serialization to XML when the module name is the same as user name - 'performance'.
verified