Bug 230468 - [EditorMgmt] UI Parts References Tests get 'unable to create editor' messages
Summary: [EditorMgmt] UI Parts References Tests get 'unable to create editor' messages
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-06 15:21 EDT by Eric Moffatt CLA
Modified: 2019-09-06 16:06 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2008-05-06 15:21:40 EDT
The 'EditorsReferencesTest' when running gets a 'error' editor instead of a real one for every test except the first one. The error message is 'Cannot open editor, Device is disposed'.

This is occurring -with- Boris' patch for the prefs (i.e. the RCP tests now work)
Comment 1 Eric Moffatt CLA 2008-05-06 15:22:36 EDT
BTW, these tests appear to pass (likely because we open the error editor so the correct 'part' is active).
Comment 2 Paul Webster CLA 2008-05-06 15:38:47 EDT
I think this is a pre-existing problem with the tests (not caused by recent changes)

PW
Comment 3 Boris Bokowski CLA 2008-05-06 21:40:02 EDT
(In reply to comment #2)
> I think this is a pre-existing problem with the tests (not caused by recent
> changes)

Sounds likely. We might have a similar problem to what I fixed today, some cache holding on to disposed resources.
Comment 4 Eric Moffatt CLA 2008-05-13 09:22:19 EDT
Boris, I've been watching these tests during the submission testing and I've seen it run correctly at least once (i.e. all the editors open, no 'error' parts).
Comment 5 Boris Bokowski CLA 2009-11-17 13:01:44 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:06:49 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.