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.
Product Version = NetBeans IDE Dev (Build 200211080100) IDE Versioning = IDE/1 spec=3.18 impl=200211080100 Operating System = Linux version 2.4.18 running on i386 Java; VM; Vendor = 1.4.1_01; Java HotSpot(TM) Client VM 1.4.1_01-b01; Sun Microsystems Inc. Java Home = /usr/java/j2sdk1.4/sun/jdk1.4.1_01/jre System Locale; Encod. = cs_CZ; ISO-8859-2 Home Dir; Current Dir = /home.local/danielm; /DISKS/storage3/forte/NBdev-last/netbeans/bin IDE Install; User Dir = /home.local/danielm/NBdev-last; /home.local/danielm/.netbeans/dev ------------------------------------------------------------------------------- This occures very rearly. But the fact it happens sometimes is enough to enter it as a bug. For JavaCVSValidationTest suite it is critical 'cause it causes that test fails. But it happens rearly as I said -> P5 (is it OK?) How it happens? =============== If you commit a file using build-in cvs client first CommandOutputWindow is oppened. After command is finished the button KILL is changed to CLOSE and in MainWindow you could see: Finished: Commit Close the CommandOutputWindow and see if file status has changed: in my case- NOT:-((( In CVS/Entries there is vriten right revision so, that is a bugy inicialication of setting correctly filestatuses... Don't know what all you;d like I included here as an evidence. So, first the picture then log of failed test, jemmy log and CVS/* and if I succed something more like whole working....
Created attachment 7893 [details] picture of problematic file in Explorer
Created attachment 7894 [details] Packed CVSWorkingDir....please, be interested in this dir: testdir5721
Created attachment 7896 [details] testlog of failed test case
it is still happening (SOMETIMES, but quiet often) and also it is reproductable by hand... see the TestSpec at: http://javacvs.netbeans.org/qa/testspecs/s1s5/JavaCVSTestSpecification.html and TC $4 action #8 Well I have to say (according this TC) that only 3 files and 1 dir had been added and after that commited. And it took a lot of time to became for them to be [Up-to-date] ... I could say more then 5-10minutes after they were commited. So some kinda strange lazy refresh statuses afetr commit must been performed... but this so long time is unacceptable.... for normal usage... I'm increasing the priority to P4
As described at http://www.netbeans.org/servlets/ReadMsg?msgId=655179&listName=nbusers the development of javacvs module has been stopped.