August 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 2.0] #20262

by Marcus Denker

On Aug 21, 2012, at 2:52 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > The image is broken, it cannot add new methods :( > it requires to add MethodAdded>>newMethod or similar hack > The strange thing is that it worked. What I did was: -> DL the image (after tests where run on Mac and linux, so it works) -> Ran "ScriptLoader new cleanUpForRelease" -> put that image on gforge -> used it as the seed for jenkins The resulting image now has problems, I have no idea why. > -- Pavel > > On Tue, Aug 21, 2012 at 12:58 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> 20262 >> ----- >> >> Issue 6585: Fuel has ref to non-existing FLPackageLoader >> http://code.google.com/p/pharo/issues/detail?id=6585 >> >> Issue 6582: ComposableModel >> #instantiateModels: is broken >> http://code.google.com/p/pharo/issues/detail?id=6582 >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

Re: [Pharo-project] [update 2.0] #20262

by Pavel Krivanek

The image is broken, it cannot add new methods :( it requires to add MethodAdded>>newMethod or similar hack -- Pavel On Tue, Aug 21, 2012 at 12:58 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20262 > ----- > > Issue 6585: Fuel has ref to non-existing FLPackageLoader > http://code.google.com/p/pharo/issues/detail?id=6585 > > Issue 6582: ComposableModel >> #instantiateModels: is broken > http://code.google.com/p/pharo/issues/detail?id=6582 > > -- > Marcus Denker -- http://marcusdenker.de > >

Aug. 21, 2012

Re: [Pharo-project] CI Tests ?

by Marcus Denker

On Aug 21, 2012, at 2:43 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Hi, > > I noticed that although 2.0 images are being built multiple times a day, the tests have not been running for 9 days. > > Does anyone know what the problem is and how this could be fixed ? > Yes, the windows slave is down. > It kind of defeats the purpose of a CI server when no tests are run. Indeed. Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

[Pharo-project] CI Tests ?

by Sven Van Caekenberghe

Hi, I noticed that although 2.0 images are being built multiple times a day, the tests have not been running for 9 days. Does anyone know what the problem is and how this could be fixed ? It kind of defeats the purpose of a CI server when no tests are run. Thx, Sven

Aug. 21, 2012

[Pharo-project] shortDebugStackOn: is TOO short

by Mariano Martinez Peck

ContextPart >> #shortDebugStackOn: aStream "print the top ten contexts on my sender chain." ^ self debugStack: 10 on: aStream I think it is useless. It is really difficult to understand what is happening with only 10 elements of the stack. Can we put, say 20 or 30 ? Thanks -- Mariano http://marianopeck.wordpress.com

Aug. 21, 2012

[Pharo-project] pharo-2.0-tests Â» 32,mac - Build # 308 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Aug. 21, 2012

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 308 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Aug. 21, 2012

[Pharo-project] [update 2.0] #20262

by Marcus Denker

20262 ----- Issue 6585: Fuel has ref to non-existing FLPackageLoader http://code.google.com/p/pharo/issues/detail?id=6585 Issue 6582: ComposableModel >> #instantiateModels: is broken http://code.google.com/p/pharo/issues/detail?id=6582 -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

[Pharo-project] [update 2.0] #20261

by Marcus Denker

20261 ----- Issue 6587: FileSystem API Improvement http://code.google.com/p/pharo/issues/detail?id=6587 -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

Re: [Pharo-project] Trait conflicts wtf?

by StÃ©phane Ducasse

Mariano Mail communication is difficult and takes much more energy than face to face. I do not have this energy now and answer a good answer, so we can talk at esug or via chat (voice) no text for me. What I remember is that there is a problem in the trait implementation but I do not remember it. Damien C. should know it. Stef > We forgot to say that the motivation of this is that if we throw an error or take an assumption on how to resolve the conflict, plus some other changes we already done, we should be able to NOT use the Compiler at all when installing traits. The only place where we would still need the Compiler is when using Alias, but so far we have only ONE user in the image and it is TPureBehavior. Meaning that with this changes, in the 99.99% of the cases (it only uses Compiler when importing Traits with aliases) we can have kernels and boostraped images that can grow (even with traits) without the compiler. > Anyway, besides this "benefit", we didn't like that it silently fails and creates a method saying "self traitConflict". > Maybe we are not saying something.... > > Cheers, > > On Mon, Aug 20, 2012 at 4:48 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Mon, Aug 20, 2012 at 4:46 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Trait named: #TA > uses: {} > category: 'ABC' > > Trait named: #TB > uses: {} > category: 'ABC' > > > TA>>a > ^10 > > TB>>a > ^10 > > Object subclass: #A > uses: TA + TB > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'ABC' > > ==> > > A>>a > ^self traitConflict > > > ? > > Why not an exception from a conflictive composition? This is to Mariano me a silent failure :/ > > > Or assume a resolution (like when selectors of classes have precedence over trait methods) > > > Guille > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Aug. 21, 2012