Bugzilla – Full Text Bug Listing
| Summary: | [eclipse-build] [tests] 3 failures, 1 error in org.eclipse.jdt.ui.tests LeakTestSuite (x86_64; Fedora 12; 0.4RC5) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Andrew Overholt <overholt> | ||||
| Component: | eclipse-build | Assignee: | Packaging Tools Inbox <linux.packagingtools-inbox> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | akurtakov | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 295095 | ||||||
| Attachments: |
|
||||||
|
Description
Andrew Overholt
Created attachment 152192 [details]
JUnit report
Also known to fail on: x86, Fedora 11, eclipse-build trunk 2009-09-24 (3.5.0) x86, Fedora rawhide (12), eclipse-build trunk 2009-10-05 (3.5.1) x86, Debian unstable 2009-10-07, eclipse-build trunk 2009-10-07 (3.5.1) testTextEditorClose() , testTextEditorCloseOneOfTwo(), and testTextEditorCloseAll() seem to fail due to the existence of org.eclipse.ui.tests.commands.EditorActionDelegate. Running the plugin with org.eclipse.ui.tests closed seems to fix those 3 test failures. EditorActionDelegate stores a reference to the active text editor. When a test case closes its text editor and sets the variable to null, the EditorActionDelegate still has a reference to the editor and so the object is never destroyed. This results in there being one TextEditor object existing when there should be none. How does org.eclipse.ui.tests.commands.EditorActionDelegate end up in the test workspace? Is it from a previous test suite? I thought we were deleting the workspace contents between suite runs. I don't think EditorActionDelegate is still in the workspace afterwords, as everything in testDataDir home and testHome gets removed per testsuite launch. I think the fact that it is located in ${basedir}/build/eclipse-${buildTag}-fetched-src/testsInstallation/eclipse/plugins/ may be the issue.
I tried :
[tester@localhost plugins]$ pwd
/home/tester/eclipse-build-test/eclipse-build/build/eclipse-R3_5_1-fetched-src/testsInstallation/eclipse/plugins
[tester@localhost plugins]$ mv org.eclipse.ui.tests* ../
After running just the org.eclipse.jdt.ui.tests this resulted in the 3 test cases in question passing.
Hmm. That's odd. I *guess* we could work around it by not installing (with the p2 director) all of the test plugins at the same time. But that seems hacky. Closing this bug as it was not worked on and it's really outdated now. |