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.
testMove1: java.lang.NullPointerException at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.renameChildren(NamingFactory.java:92) at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.rename(NamingFactory.java:80) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.BaseFileObj.rename(BaseFileObj.java:195) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObj.rename(FileObj.java:268) at org.netbeans.modules.masterfs.MasterFileObject.rename(MasterFileObject.java:575) at org.netbeans.modules.masterfs.MasterFileObject.move(MasterFileObject.java:501) at org.openide.filesystems.FileObjectTestHid.testMove1 (FileObjectTestHid.java:197)
Created attachment 33235 [details] the failure
http://beetle.czech:8080/unittest/TestCase.jsp?issues=4124 http://beetle.czech:8080/unittest/TestCase.jsp?issues=4125 http://beetle.czech:8080/unittest/TestCase.jsp?issues=4126 http://beetle.czech:8080/unittest/TestCase.jsp?issues=4127
Yes, these tests fails in 5.5 on Windows and only with subversion enabled.
Also this test fails: http://beetle.czech:8080/unittest/TestCase.jsp?issues=4130 All these tests simulate subversion behaviour: ignore while deleting folders containing metadata for subversion.
#85862 fixed. So, the only failing test should remain MasterFileSystemWithExtensionsTest.testSimulatesRefactoringRename which actually simulates refactoribg rename but just with subversion tricky extensions. This problem may happen (but not reported yet) just when subversion module is installed via AU and used for rename. This test will be disabled for release55. Jarda, do you agree as reporter ?
I agree.
Created attachment 34689 [details] test diabled in dfg-unit.xml
/cvs/openide/masterfs/test/cfg-unit.xml,v <-- cfg-unit.xml new revision: 1.1.124.2; previous revision: 1.1.124.1 For release 55 - close as WONTFIX and test removed.