| Summary: | [Unit Test Failure] org.eclipse.gmt.modisco.infra.browser.custom.tests.BrowserCustomTest.testUICustomWithCondition | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] MoDisco | Reporter: | Gregoire Dupe <gdupe> | ||||
| Component: | Infrastructure | Assignee: | Nicolas Bros <nicolas.bros> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | fabien.giquel, hugo.bruneliere, modisco.web-inbox, nicolas.bros | ||||
| Version: | 0.9.0 | Flags: | gdupe:
indigo+
|
||||
| Target Milestone: | 0.9.0 M2 | ||||||
| Hardware: | Power PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Gregoire Dupe
Hi, In revision 2814, I’ve added a unit test to check that the class Display can be used Regards, Grégoire Dupé The unit test org.eclipse.gmt.modisco.infra.browser.custom.tests.BrowserCustomTest.checkDisplay also failed.
Here is the unit test checkDisplay source code :
public void checkDisplay() {
Display.getCurrent();
}
I suppose that there is a problem with the Eclipse set up.
Regards,
Grégoire Dupé
I changed the test so that it doesn't trigger the "display problem" on build.eclipse.org. Bug fixed. |