Bug 143883 - Non-deterministic transform results
Summary: Non-deterministic transform results
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: gmt (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: gmt-atl-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-26 01:33 EDT by Ed Willink CLA
Modified: 2017-04-11 15:13 EDT (History)
0 users

See Also:

Attachments
Repro (11.29 KB, application/octet-stream)
2006-05-26 01:34 EDT, Ed Willink CLA 		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 Ed Willink CLA 2006-05-26 01:33:20 EDT 
The attached example (next merssage) gives different results on successive run attempts. (The source model contains 4 Relation instances. The result contains
between 0 and 4 transformed instances.)

Repeatable on Eclipse 3.1 or 3.2RC5 with corresponding EMF.

Using ATL from CVS as at 25-May-2006 with Dennis' https://bugs.eclipse.org/bugs/show_bug.cgi?id=140546
patch.
Comment 1 Ed Willink CLA 2006-05-26 01:34:20 EDT 
Created attachment 42678 [details]
Repro
Comment 2 Ed Willink CLA 2006-06-03 07:02:30 EDT 
The non-determinism was caused by how much got done before a crash.

The crash was caused by iteration over a collection of undefined's.

Changing

ASMOclUndefined.java

	public ASMOclAny get(StackFrame frame, String name) {
		frame.printStackTrace("ERROR: OclUndefined has no property");
		return null;
	}

to

	public ASMOclAny get(StackFrame frame, String name) {
		frame.printStackTrace("ERROR: OclUndefined has no property: '" + name + "'");
		return null;
	}

would at least improve the chances of understanding the buried diagnostic.