[Pharo-dev] Pharo5 Jenkins build crash

2016-08-09 Thread Yann Dubois
Hi,

Since Sunday, all build launched for Pharo 5 crashed

I have this log message :




CollectionIsEmpty: a Set() is emptySet(Collection)>>errorEmptyCollection
Set(Collection)>>emptyCheck
Set(Collection)>>anyOne
Set(Collection)>>sum:
TestCommandLineHandler>>informResults:
TestCommandLineHandler>>runPackages
TestCommandLineHandler>>activate
TestCommandLineHandler class(CommandLineHandler class)>>activateWith:
[ aCommandLinehandler activateWith: commandLine ] in
PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand:
in Block: [ aCommandLinehandler activateWith: commandLine ]
BlockClosure>>on:do:
PharoCommandLineHandler(BasicCommandLineHandler)>>activateSubCommand:
PharoCommandLineHandler(BasicCommandLineHandler)>>handleSubcommand
PharoCommandLineHandler(BasicCommandLineHandler)>>handleArgument:
[ self
handleArgument:
(self arguments
ifEmpty: [ '' ]
ifNotEmpty: [ :arguments | arguments first ]) ] in
PharoCommandLineHandler(BasicCommandLineHandler)>>activate in Block: [
self...
BlockClosure>>on:do:
PharoCommandLineHandler(BasicCommandLineHandler)>>activate
PharoCommandLineHandler>>activate
PharoCommandLineHandler class(CommandLineHandler class)>>activateWith:
[ super activateWith: aCommandLine ] in PharoCommandLineHandler
class>>activateWith: in Block: [ super activateWith: aCommandLine ]
NonInteractiveUIManager(UIManager)>>defer:
PharoCommandLineHandler class>>activateWith:
[ aCommandLinehandler activateWith: commandLine ] in
BasicCommandLineHandler>>activateSubCommand: in Block: [
aCommandLinehandler activateWith: commandLine ]
BlockClosure>>on:do:
BasicCommandLineHandler>>activateSubCommand:
BasicCommandLineHandler>>handleSubcommand
BasicCommandLineHandler>>handleArgument:
[ self
handleArgument:
(self arguments
ifEmpty: [ '' ]
ifNotEmpty: [ :arguments | arguments first ]) ] in
BasicCommandLineHandler>>activate in Block: [ self...
BlockClosure>>on:do:
BasicCommandLineHandler>>activate
[ self new activate ] in BasicCommandLineHandler class>>startUp: in
Block: [ self new activate ]
./pharo $JOB_NAME.image config
http://smalltalkhub.com/mc/NorbertHartl/Mustache/main
ConfigurationOfMustache --install=bleedingEdge
+ ./pharo Pillar.image config
http://smalltalkhub.com/mc/NorbertHartl/Mustache/main
ConfigurationOfMustache --install=bleedingEdge
'Installing ConfigurationOfMustache bleedingEdge'Error:
MessageNotUnderstood: receiver of "finish" is
nilUndefinedObject(Object)>>error:
[ :err :rcvr |
| errCtx errMorph |
errCtx := thisContext.
[ errCtx := errCtx sender.
"Search the sender chain to find the morph causing the problem"
[ errCtx notNil and: [ errCtx receiver isMorph not ] ]
whileTrue: [ errCtx := errCtx sender ].
"If we're at the root of the context chain then we have a fatal drawing problem"
errCtx ifNil: [ ^ self handleFatalDrawingError: err ].
errMorph := errCtx receiver.
"If the morph causing the problem has already the #drawError flag set,
then search for the next morph above in the caller 
chain."
errMorph hasProperty: #errorOnDraw ] whileTrue.
errMorph setProperty: #errorOnDraw toValue: true.
"Install the old error handler, so we can re-raise the error"
rcvr error: err ] in WorldState>>displayWorldSafely: in Block: [ :err
:rcvr | ...
BlockClosure>>cull:cull:
[ :ex | errorHandlerBlock cull: ex description cull: ex receiver ] in
BlockClosure>>ifError: in Block: [ :ex | errorHandlerBlock cull: ex
description cul...etc...
BlockClosure>>cull:
Context>>evaluateSignal:
Context>>handleSignal:
MessageNotUnderstood(Exception)>>signal
UndefinedObject(Object)>>doesNotUnderstand: #finish
WorldState>>displayWorld:submorphs:
WorldMorph>>displayWorld
[ aWorld displayWorld ] in WorldState>>displayWorldSafely: in Block: [
aWorld displayWorld ]
BlockClosure>>on:do:
BlockClosure>>ifError:
WorldState>>displayWorldSafely:
WorldState>>doOneCycleNowFor:
WorldState>>doOneCycleFor:
WorldMorph>>doOneCycle
[ [ World doOneCycle.
Processor yield.
false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in
Block: [ [ World doOneCycle
[ self value.
Processor terminateActive ] in BlockClosure>>newProcess in Block: [
self value





I think that the problem is in command line handler but I'm not sure.
You can see the complete log, for example, at
https://ci.inria.fr/pharo-contribution/job/Pillar/1715/PHARO=50,VERSION=stable,VM=vm/console


Re: [Pharo-dev] new collaborators in Pharo 5

2016-05-02 Thread Yann Dubois
Im not on the list, whereas I worked with Maxime Roeland on 2 bugs during
the Sprint :)

2016-04-29 10:25 GMT+02:00 Esteban Lorenzano :

> Hi,
>
> So, according to my script, this are the new collaborators (people who
> started contributing after 1st march 2015):
>
> Maxleske
> CyrilFerlicot
> Latsabben
> Nicolaihess
> synectique
> BorisSpasojevic
> Stef
> Bite
> hn
> SvenVanCaekebenberghe
> StefnReichhart
> NicoPasserini
> DEMAREYChristophe
> HenrikNergrd
> SkipLentz
> Spirita
> Fuel
> TravisCI
> HolgerHansPeterFreyther
> SpurBootstrap
> qdq
> SergioFedi
> jeanbaptisteArnaud
> AutoGenTutorial
> PabloTesone
> ThomasHeniart
> ValentinRyckewaert
> mml
> HenrikNergaard
> MarcusDenkr
> DenisKudriashov
> Alexandre
> mcamp
> Matthieu
> w3ertyu
> VincentBlondeauAbdelghaniAlidra
> TH
> MerwanOuddane
> ChristopherCoat
> AlainRastoul
> FranckWarlouzet
> AbdelghaniLaidra
> ThibaultArloing
> pad
> RogerStebler
> DavidAllouche
> RM
> tr
>
> Obviously… many are wrong since they started contributing a lot before
> (like Sven and Stef :P … I wonder why the difference gave me this… but
> well… )
>
> Anyway, I need to know who are this guys:
>
> - synectique (I suppose is Guillome, Usman or Cyril)
> - Bite (I hope this is not a french guy, because in that case is soo
> rude… or proud of himself :P)
> - hn
> - Spirita
> - qdq
> - mml
> - Alexandre (Bergel?)
> - mcamp
> - Matthieu
> - w3ertyu
> - TH
> - pad
> - RM
> - tr
>
> So… any hints about authors?
>
> thanks,
> Esteban
>


Re: [Pharo-dev] Pillar replacement for PRDocumentParser ?

2016-06-01 Thread Yann Dubois
You use the development version or the stable ?
Le 1 juin 2016 18:26, "Esteban Lorenzano"  a écrit :

> Hi,
>
> recent versions of Pillar do not have PRDocumentParser anymore… someone
> knows what should I use?
>
> thanks!
> Esteban
>
>
>


Re: [Pharo-dev] Pillar replacement for PRDocumentParser ?

2016-06-01 Thread Yann Dubois
When I want parse something in Pillar, I do :

PRDocument parser parse: myString

It should work.

2016-06-01 19:13 GMT+02:00 Esteban Lorenzano :

> stable
>
> On 01 Jun 2016, at 18:47, Yann Dubois  wrote:
>
> You use the development version or the stable ?
> Le 1 juin 2016 18:26, "Esteban Lorenzano"  a écrit :
>
>> Hi,
>>
>> recent versions of Pillar do not have PRDocumentParser anymore… someone
>> knows what should I use?
>>
>> thanks!
>> Esteban
>>
>>
>>
>


Re: [Pharo-dev] Pillar configuration bug ?

2016-06-06 Thread Yann Dubois
I add two groups :

- parser : To load the Pillar parser
- parser tests : To testing the parser

Yann

2016-06-04 11:45 GMT+02:00 Cyril Ferlicot D. :

> Le 03/06/2016 14:51, Esteban Lorenzano a écrit :
> > Without the parser you can’t do anything so I would expect the parser to
> be a core part.
> > But anyway, even agreeing with your PoV, if I load #(html exporter),
> then I have unreferenced pillar classes in the resulting image
> (PRDocumentItem class>>#parser has a strong reference… and even that method
> should not be there according with your statement).
> >
> > but anyway, for me the important part is: what do I need to load to have
> the parser? there is no group “parser” in ConfigurationOfPillar.
> >
> > cheers!
> > Esteban
> >
> >
> >
>
> Hi Esteban,
>
> I agree with Damien that we might want the Model and exporter without
> the parser.
>
> If the parser is missing as a group, this is a problem. The strong
> reference was removed already in the development version.
>
> I wall open an issue to let Yann and Thibault see the problem and
> correct it :)
>
> --
> Cyril Ferlicot
>
> http://www.synectique.eu
>
> 165 Avenue Bretagne
> Lille 59000 France
>
>