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

Bug 366848

Summary:	[releng] Fix Impact Analyzer test cases
Product:	[Modeling] OCL	Reporter:	Adolfo Sanchez-Barbudo Herrera <adolfosbh>
Component:	Core	Assignee:	OCL Inbox <mdt-ocl-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, ed
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Adolfo Sanchez-Barbudo Herrera

2011-12-15 12:50:23 EST

The Impact Analyzer tests are not working in hudson. They are temporally deactivated.

Investigate the causes of this.

Comment 1 Axel Uhl

2011-12-15 14:53:31 EST

Starting with which commit did they fail?

Comment 2 Ed Willink

2011-12-15 15:02:38 EST

I think that they have never worked in the separate Tools/Core builds.

From the error message, it looked like perhaps it's just a missing plugin (reference).

Comment 3 Adolfo Sanchez-Barbudo Herrera

2011-12-16 08:12:47 EST

(In reply to comment #2)
> I think that they have never worked in the separate Tools/Core builds.
> 

Exactly.

> From the error message, it looked like perhaps it's just a missing plugin
> (reference).

I'm working on this. Firstly trying to make the test cases work in my local workspace (creating and using the target platform via buckminster, in the same fashion is made by hudson).

I'll let you know my progress.

Regards,
Adolfo.

Comment 4 Adolfo Sanchez-Barbudo Herrera

2011-12-16 14:20:21 EST

EventManager and Impact Analyzer Junit launching were expecting a product definition which looks like to not be present in the target platform (hence not required to build OCL).

Configuring the Junit launching as a simple headless application has made the trick

P.S: I'm wondering why examples.tests and examplex.xtest.tests are passing/being executed if they also are supposed to run the org.eclipse.sdk.ide product .... any light here ?
P.S2: --stderr and --stdout flags in the junit buckminster command, helps to debug this kind of errors.

Changes has been (obviously) pushed to master. Commits range: 
- 44334b43908b58d82a18fef59bfe844f407f5fa8 to 5a5d133976dac4eb39d1151d581b20885d4ab224

Resolving as fixed.

Cheers,
Adolfo.

Comment 5 Adolfo Sanchez-Barbudo Herrera

2011-12-16 14:21:58 EST

> Changes has been (obviously) pushed to master. Commits range:
> - 44334b43908b58d82a18fef59bfe844f407f5fa8 to
> 5a5d133976dac4eb39d1151d581b20885d4ab224
> 
Apologies. The first commit in the range was wrong. The correct one:

- 1ee0044edad98926fea7d3d2b8b7946083806e06 to 5a5d133976dac4eb39d1151d581b20885d4ab224

Comment 6 Ed Willink

2013-05-20 11:37:02 EDT

CLOSED after a year in the RESOLVED state.