[Pharo-project] Emergency evaluator pops up on red tests
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
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
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
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
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
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
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
PPPHPCoreGrammar ignoredNames #('properties' 'parser' 'keywords') browseSelectorsOn: aBrowser aBrowser list title: 'Productions'; format: [ :class | class asString ]; display: [ :class | ((((class allInstVarNames copyWithoutAll: class ignoredNames) copyWithoutAll: self rootClass allInstVarNames) collect: [ :each | each asSymbol ]) select: [ :each | class includesSelector: each ]) asSortedCollection ]; selectionAct: [ StandardToolSet ^^^^^^^^ does not exist anymore in 1.4 I guess but this is should not be related to this bug. -> use Smalltalk tools browser browse: self selectedClass selector: self selectedSelector ] on: $b entitled: 'browse (b)'; selectionAct: [ | class selector | class := self selectedClass. selector := self selectedSelector. (class instVarNames includes: selector) ifTrue: [ class removeInstVarName: selector ]. class removeSelector: selector. aBrowser entity: self rootModel. self selectedClass: class ] on: $r entitled: 'remove (x)'
Hi, Thanks a lot for your effort. It is really strange that just the PHP parser doesn't work. In fact all the parsers I implemented use the same mechanism to ignore instance variables names not related to parsers (so the ignoredNames). Tomorrow morning I will try again to play with the bug. Please let me know if I can do something to help. Thanks a lot again. Cheers, Fabrizio 2012/3/30 Stéphane Ducasse <stephane.ducasse@inria.fr>
PPPHPCoreGrammar ignoredNames #('properties' 'parser' 'keywords')
browseSelectorsOn: aBrowser aBrowser list title: 'Productions'; format: [ :class | class asString ]; display: [ :class | ((((class allInstVarNames copyWithoutAll: class ignoredNames) copyWithoutAll: self rootClass allInstVarNames) collect: [ :each | each asSymbol ]) select: [ :each | class includesSelector: each ]) asSortedCollection ]; selectionAct: [ StandardToolSet ^^^^^^^^ does not exist anymore in 1.4 I guess but this is should not be related to this bug.
-> use Smalltalk tools browser
browse: self selectedClass selector: self selectedSelector ] on: $b entitled: 'browse (b)'; selectionAct: [ | class selector | class := self selectedClass. selector := self selectedSelector. (class instVarNames includes: selector) ifTrue: [ class removeInstVarName: selector ]. class removeSelector: selector. aBrowser entity: self rootModel. self selectedClass: class ] on: $r entitled: 'remove (x)'
participants (2)
-
Fabrizio Perin -
Stéphane Ducasse