321571 – [Unit Test Failure] org.eclipse.gmt.modisco.infra.browser.custom.tests.BrowserCustomTest.testUICustomWithCondition

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321571 - [Unit Test Failure] org.eclipse.gmt.modisco.infra.browser.custom.tests.BrowserCustomTest.testUICustomWithCondition

Summary: [Unit Test Failure] org.eclipse.gmt.modisco.infra.browser.custom.tests.Browse...

Status:	CLOSED FIXED

Alias:	None

Product:	MoDisco
Classification:	Modeling
Component:	Infrastructure (show other bugs)
Version:	0.9.0
Hardware:	Power PC Linux

Importance:	P1 normal (vote)
Target Milestone:	0.9.0 M2
Assignee:	Nicolas Bros
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-08-03 06:24 EDT by Gregoire Dupe
Modified:	2010-10-18 08:36 EDT (History)
CC List:	4 users (show)

See Also:

Flags:	gdupe: indigo+

Attachments
Details (9.15 KB, text/plain) 2010-08-03 06:24 EDT, Gregoire Dupe	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Gregoire Dupe

2010-08-03 06:24:33 EDT

Created attachment 175759 [details]
Details

The unit test org.eclipse.gmt.modisco.infra.browser.custom.tests.BrowserCustomTest.testUICustomWithCondition  fails.

Cf. https://build.eclipse.org/hudson/job/modisco-nightly/87/testReport/junit/org.eclipse.gmt.modisco.tests.AllTests$org.eclipse.gmt.modisco.infra.browser.custom.tests.AllTests$org.eclipse.gmt.modisco.infra.browser.custom.tests/BrowserCustomTest/testUICustomWithCondition/

Comment 1 Gregoire Dupe

2010-08-03 06:29:10 EDT

Hi,

In revision 2814, I’ve added a unit test to check that the class Display can be used

Regards,
Grégoire Dupé

Comment 2 Gregoire Dupe

2010-08-03 09:04:07 EDT

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é

Comment 3 Nicolas Bros

2010-09-09 08:51:09 EDT

I changed the test so that it doesn't trigger the "display problem" on build.eclipse.org.

Comment 4 Hugo Bruneliere

2010-10-05 04:32:15 EDT

Bug fixed.