Re: [Pharo-project] Emergency evaluator pops up on red tests

March 30, 2012

      Igor could you have a look because it looks to me that this is a bug in the primitiveError: method or friend.
This is also strange since the ignoredNames method is a class method so PPTrimmingParser>>ignoredNames
looks wrong to me.

openDebuggerOn: process context: context label: title contents: contentsStringOrNil fullView: bool 
	"Open a notifier in response to an error, halt, or notify. A notifier view
	just shows a short view of the sender stack and provides a menu that
	lets the user open a full debugger."
	| errorWasInUIProcess |
	errorWasInUIProcess := self spawnNewProcessIfThisIsUI: process.
	[Smalltalk tools debugger logDebuggerStackToFile
		ifTrue: [Smalltalk
				logError: title
				inContext: context ]] on: Error do: [].
	WorldState
		addDeferredUIMessage: [[| debugger | 
			debugger := Smalltalk tools debugger new
						process: process
						controller: nil
						context: context.
			"schedule debugger in deferred UI message to address
			redraw problems after opening a debugger e.g. from
			the testrunner."
			"WorldState addDeferredUIMessage: ["
			bool
				ifTrue: [debugger openFullNoSuspendLabel: title]
				ifFalse: [debugger openNotifierContents: contentsStringOrNil label: title].
			debugger errorWasInUIProcess: errorWasInUIProcess.]
				on: Error
				do: [:ex | Debugger primitiveError: 'Orginal error: ' , title asString , '.
	Smalltalk tools debugger error: '
							, ([ex description]
									on: Error
									do: ['a ' , ex class printString]) , ':']].

	process suspend.

Stef
...
Now when try to execute
CoreGammar>>testAbstract I get an emergency evaluator
PPTrimmingParser>>ignoredNames
Smalltalk tools debugger error
I will try to investigate more
Stef
On Mar 30, 2012, at 9:53 PM, StÃ©phane Ducasse wrote:
...
Hi fabrizio
when I run PPPHPCoreGrammarTests I got 488 run and 448 errors but no emergency evaluator.
I used the image you mentioned and the VM probably from the Moose-1.app
I could also run all the tests.
Stef
On Mar 30, 2012, at 9:49 PM, StÃ©phane Ducasse wrote:
...
ok I'm trying now
:)
On Mar 30, 2012, at 6:55 PM, Fabrizio Perin wrote:
...
Hi Stef,
I just tried to evaluate in a workspace as you said and i've got the same result. Also by executing the test in Nautilus with cmd-t i've got the same.
Cheers,
fabrizio
On Mar 30, 2012 3:30 PM, "StÃ©phane Ducasse" <stephane.ducasse@inria.fr> wrote:
did you try to run on single test manually
Test debug:#l';l;k;lk;l2
Stef
On Mar 30, 2012, at 1:28 PM, Fabrizio Perin wrote:
...
Hi,
I loaded all my stuff in the latest moose based on 1.4.
All the tests of my PetitPHPParser are red. When I click on one red method the emergency evaluator pops up.
To reproduce it:
1- grab the latest MooseJee from the ci:
http://ci.moosetechnology.org/job/moose-latest-dev/
2- load the petit php parser:
Gofer new
 squeaksource: 'PetitPHPParser';
 package: 'ConfigurationOfPetitPHPParser';
 load.
(Smalltalk at: #ConfigurationOfPetitPHPParser) perform: #loadDefault.
3- Run the tests of the php parser and click on any red method.
How can I debug the problem? Any suggestions on how to proceed?
Thanks,
Fabrizio