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.
Deadlock in DataFolderMoveTest. This deadlock seems to be reproducible on my mashine so markin P2 - feel free to lower. See thread dump in the attachment (second dump).
This can be related to issue #8705.
Created attachment 4580 [details] ftd
The problem is that the main thread of calling some method that should be called from AWT thread. This is the problem of this test only and does not affect users. The DataFolderMoveTest is currently in the "always failing tests" section in openide unit tests anyway. I am going improve the test. Changing the priority -> P4.
Closing as WORKSFORME. 1) I am running tests very often and without this deadlock. I have never reproduced it. 2) The thread dump is strange and doesn't show a real deadlock - main thread is waiting in constructor of Mutex$ThreadInfo, FolderRecognizer is waiting in HashMap (which is not synchronized).
The deadlock still happens quite frequently, at least on Solaris. I'll attach a thread dump as soon as it will happen to me again.
Happens to me often on Solaris8. Please remove this test from stable tests because this test blocks qa lab machine.
Created attachment 5480 [details] Thread dump
Test excluded from trunk stable test execution.
Set target milestone to TBD
I need more info for this to be resolved: 1. JDK version (exact) 2. does it still happen (FolderChildren has been changed recently)? Marking as invalid (bug report) for now. Feel free to reopen after adding the required info.
Without new informations for long time - so verifying, closing.