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.
Our hudson job [1] that tests new classes loaded during startup with an opened Java SE project [2] started to fail - there're more than 100 new classes. We'd appreciate help with part of the list - to analyze classes that belong to editor and java (lang.) infrastructure. This means to go through the list [3] [4] and decide which classes are ok (add them to whitelist) and which are suspicious (file a bug). Please have in mind these classes were not loaded before so consider if it's ok there are now loaded after IDE starts with a project (no file opened in editor). Thanks for help. BTW we're observing about 10% regression since 6.8 in this startup scenario, reducing the classes may help here (though we don't know the exact impact). [1] Hudson job: http://deadlock.netbeans.org/hudson/job/ergonomics/ [2] Tested project: http://hg.netbeans.org/binaries/FDCBE13B6CA7B154F6EE29BEF3B9404F7A7B1A57-lime6.zip [3] the list of new classes: http://deadlock.netbeans.org/hudson/job/ergonomics/lastSuccessfulBuild/artifact/ide.kit/build/test/qa-functional/work/o.n.t.i.W/testWhitelist3/whitelist_violators_3.txt [4] the list also with stacktraces: http://deadlock.netbeans.org/hudson/job/ergonomics/lastSuccessfulBuild/artifact/ide.kit/build/test/qa-functional/work/o.n.t.i.W/testWhitelist3/violations_3.xml
The indexers are tracked as 187271. This report is about the rest of the classes in the report.
we will do evaluation for newer tests - closing