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.
Randomly I got the following exception at the end of running my unit tests on http://wizard.dev.java.net - first time I've seen it - probably some sort of race condition with file deletion. java.lang.IllegalStateException: The data object MasterFileObject@1fbdddf[C:/space/wizard/junit712969869.properties] is invalid; you may not call getNodeDelegate on it any more; see #17020 and please fix your code at org.openide.loaders.DataObject.getNodeDelegate(DataObject.java:242) at org.openide.loaders.DataObject.getClonedNodeDelegate(DataObject.java:274) at org.openide.loaders.FolderChildren.createNodes(FolderChildren.java:141) at org.openide.nodes.Children$Keys$KE.nodes(Children.java:2166) at org.openide.nodes.ChildrenArray.nodesFor(ChildrenArray.java:128) at org.openide.nodes.Children$Info.nodes(Children.java:1218) at org.openide.nodes.Children.updateAdd(Children.java:1014) at org.openide.nodes.Children.setEntries(Children.java:805) at org.openide.nodes.Children$Keys$2.run(Children.java:2052) at org.openide.util.Mutex.postRequest(Mutex.java:1141) at org.openide.util.Mutex.postWriteRequest(Mutex.java:487) at org.openide.nodes.Children$Keys.applyKeys(Children.java:2061) at org.openide.nodes.Children$Keys.setKeys(Children.java:2006) at org.openide.loaders.FolderChildren.access$500(FolderChildren.java:37) at org.openide.loaders.FolderChildren$ChildrenRefreshRunnable.run(FolderChildren.java:257) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:541) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:963)
I doubt it is a bug in module 'junit'. The module's source code does not contains substring "getNodeDelegate". The bug is probably either in module 'Properties' or in the NetBeans platform. It needs more investigation.
The exception was thrown from some module that tried to obtain a node for an invalid DataObject. The JUnit module does not do that - I consider this bug INVALID. Let me know if you can still reproduce the exception and I will help you with finding the module that causes it.