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.
Summary: | Changeset propagation broken for jet-main, cnd-main | ||
---|---|---|---|
Product: | platform | Reporter: | Jan Lahoda <jlahoda> |
Component: | Help System | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dstrupl, issues, issues, jglick, jskrivanek, jtulach, pgebauer, pjiricka |
Priority: | P1 | ||
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Output copied from the hudson on the failed testHelp test. |
Description
Jan Lahoda
2011-05-08 09:16:24 UTC
I am the one who enabled the MemoryValidationTest. I'll take a look. If we don't have solution by tomorrow ~noon, comment out the test in java.kit/nbproject/project.properties to allow propagation from your team repository. The goal of MemoryValidationTest is to fight against memory leaks not against broken functionality. Thus it is silly if the test fails "just" because JavaHelp throws an exception: NbModuleSuite has been started with failOnMessage(OFF) and failOnException(INFO). The following failures have been captured: [org.netbeans.modules.javahelp] THREAD: AWT-EventQueue-2 MSG: While trying to display: Help I'll try to suppress such behavior. The goal is to have robust test, that: 1. if we are lucky and Jemmy succeeds, verifies edit/compile/debug cycle in Java 2. if we are unlucky, does not fail Btw. I've seen: private static java.awt.Toolkit java.awt.Toolkit.toolkit-> sun.awt.X11.XToolkit@1d6768f-eventListener-> java.awt.Toolkit$ToolkitEventMulticaster@24beca-a-> java.awt.Toolkit$ToolkitEventMulticaster@50c3c9-b-> java.awt.Toolkit$SelectiveAWTEventListener@2dcb6-listener-> java.awt.LightweightDispatcher@17a6a4b-mouseEventTarget-> org.openide.text.QuietEditorPane@d8134d-model-> org.netbeans.modules.editor.NbEditorDocument@e0efd6 failure chain and I eliminated it by opening TopComponent with empty JTextArea: + TopComponent tc = new TopComponent(); + tc.setLayout(new FlowLayout()); + tc.add(new JTextArea()); + tc.open(); + tc.requestVisible(); + tc.requestActive(); in 09f5f3325550, I am not sure why it works on all builders, but not in bertram. Use hg pull -r d4208adce5f1 http://hg.netbeans.org/ergonomics to get my fix to your branch and see if it eliminates the testHelp error. Another changeset to pull: 1918a5d76e99 author : Jaroslav Tulach <jtulach@netbeans.org> date : Mon May 09 08:57:32 CEST 2011 summary : Disable testHelp, it is not essential for fighting with memory leaks in java projects and editor Looks like the build continues to fall. Disabling in ergonomics#a99cb5d871b4 feel free to pull this change set into your repository. Integrated into 'main-golden', will be available in build *201105111436* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d4208adce5f1 User: Jaroslav Tulach <jtulach@netbeans.org> Log: #198426: Ignore errors and messages |