- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Startup preferences

by Mariano Martinez Peck

Stef, the basis should be more or less the same. What has changed is mostly the directories in which they are searched, as Clement pointed out. Cheers, On Fri, Jun 21, 2013 at 8:00 PM, ClÃ©ment Bera <bera.clement(a)gmail.com>wrote: > It should be. > > You have to put the script in "~/Library/Preferences/pharo/ " > > You can check the startup script of Camillo in its github repository ( > https://github.com/dh83/script/blob/master/pharo-preferences.st) > > > 2013/6/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> Hi guys >> >> I want to write something on the preferences loading at startup. >> Now do you know if >> >> http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… >> is more or less up to date? >> >> Stef >> > > > > -- > ClÃ©ment BÃ©ra > Mate Virtual Machine Engineer > BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq* > -- Mariano http://marianopeck.wordpress.com

June 22, 2013

Re: [Pharo-dev] First shot on acceptance tests for the VM

by ClÃ©ment Bera

I have to say I love it too. :) Nice job 2013/6/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > I love that! > Thanks for pushing it. > > Stef > > On Jun 21, 2013, at 5:08 PM, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi! > > We were discussing over here about it, so I decided to finally start > something on the front of an acceptance test for our VM. > > The core idea is to stress the VM to test its stability and find bugs and > regressions. > > So I created the ci job in [1] which does: > - use latest vm > - use 2.0 latest image > - loads seaside and moose on it > - runs all tests > > Right now it runs on 6 different slaves, getting different results on > each, which we should take care about :). > > Also there are some things on it that should be improved easily: > - once 2.0 summer is released this job should use that version instead of > the "latest" 2.0 > - right now we are loading the development version of moose because moose > 4.8 is not released (but will be soon :) > > And of course, now we have them, we can improve them (and make them run > because not all of them do :D). > > Guille > > [1] https://ci.inria.fr/pharo/view/VM/job/PharoVM-AcceptanceTest/ > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 21, 2013

Re: [Pharo-dev] Barcodes

by Stephan Eggermont

Guillaume wrote: > I prefer the first one, creating a separate package depending on both. Done & merged. Now there is an ArteBar package in Artefact. Configuration not changed. Stephan

June 21, 2013

Re: [Pharo-dev] Startup preferences

by ClÃ©ment Bera

It should be. You have to put the script in "~/Library/Preferences/pharo/ " You can check the startup script of Camillo in its github repository ( https://github.com/dh83/script/blob/master/pharo-preferences.st) 2013/6/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > I want to write something on the preferences loading at startup. > Now do you know if > > http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… > is more or less up to date? > > Stef > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

June 21, 2013

Re: [Pharo-dev] Nice VM crash

by StÃ©phane Ducasse

thanks jan for the report On Jun 21, 2013, at 7:37 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi guys, > > getting bored? Looking for an excuse to play with GDB? Here we go: > > https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… > > > Okay, seriously: build 17 from Jun 17 did not crash - the Smalltalk code > was the same. Jenkins executes following script: > > === > export PATH=/usr/bin:$PATH > > IMAGE_BASE=CalipeL-S-$BUILD_NUMBER > IMAGE=$IMAGE_BASE.image > > if [ ! -r Pharo.image ]; then > wget -O- get.pharo.org | bash > fi > > ./pharo Pharo.image save $IMAGE_BASE > ./pharo $IMAGE config http://smalltalkhub.com/mc/JanVrany/CalipeL-S/main ConfigurationOfCalipeLS --install=0.1 > ./pharo $IMAGE benchmark --json -o results.json BenchmarkMicro > === > > System is running stock 32bit debian stable on VMWare ESX 5.1. > I can provide more details if you like (and ask what exactly :-) > > Best, Jan >

June 21, 2013

Startup preferences

by StÃ©phane Ducasse

Hi guys I want to write something on the preferences loading at startup. Now do you know if http://marianopeck.wordpress.com/2012/05/12/startuploader-running-startup-s… is more or less up to date? Stef

June 21, 2013

Re: [Pharo-dev] First shot on acceptance tests for the VM

by StÃ©phane Ducasse

I love that! Thanks for pushing it. Stef On Jun 21, 2013, at 5:08 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Hi! > > We were discussing over here about it, so I decided to finally start something on the front of an acceptance test for our VM. > > The core idea is to stress the VM to test its stability and find bugs and regressions. > > So I created the ci job in [1] which does: > - use latest vm > - use 2.0 latest image > - loads seaside and moose on it > - runs all tests > > Right now it runs on 6 different slaves, getting different results on each, which we should take care about :). > > Also there are some things on it that should be improved easily: > - once 2.0 summer is released this job should use that version instead of the "latest" 2.0 > - right now we are loading the development version of moose because moose 4.8 is not released (but will be soon :) > > And of course, now we have them, we can improve them (and make them run because not all of them do :D). > > Guille > > [1] https://ci.inria.fr/pharo/view/VM/job/PharoVM-AcceptanceTest/

June 21, 2013

Re: [Pharo-dev] Cloud Hosting Tip

by kilon

Thank you Paul, will take a deep look into when I choose replacement for linenode. :) -- View this message in context: http://forum.world.st/Pharo-dev-Cloud-Hosting-Tip-tp4693950p4694486.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 21, 2013

Re: [Pharo-dev] Running tests from Nautilus

by Benjamin

THe api exists in Pharo and is used by the monkey by example. Doing something on top, a usual, takes time and energy Ben On Jun 21, 2013, at 5:55 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > abergel wrote >> I have tried to enter a bug issue on https://pharo.fogbugz.com but I could >> not. In 2 minutes I could not figure out how to create a login and how to >> see the list of existing bugs. So maybe this one has already been >> reported. > > You can register at http://bugs.pharo.org/issues . It's the second link from > the top. This process would be easier if there was a permalink to that > second-link-from the top. As it is, there doesn't seem to be a way to point > people directly to where they can register... > https://pharo.fogbugz.com/f/cases/10262/Permalink-to-Penelope-registration-… > > b.t.w. my understanding was that we moved to fogbugz because google > discontinued their API, but I haven't seen any work on wrapping the fogbugz > API. Are we still deciding whether to stay with them? Otherwise, what is the > status of porting the API? I see there's > https://pharo.fogbugz.com/f/cases/10023/Update-Issue-Reporter-in-the-image-… > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-dev-Running-tests-from-Nautilus-tp4694412p46944… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 21, 2013

Nice VM crash

by Jan Vrany

Hi guys, getting bored? Looking for an excuse to play with GDB? Here we go: https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… Okay, seriously: build 17 from Jun 17 did not crash - the Smalltalk code was the same. Jenkins executes following script: === export PATH=/usr/bin:$PATH IMAGE_BASE=CalipeL-S-$BUILD_NUMBER IMAGE=$IMAGE_BASE.image if [ ! -r Pharo.image ]; then wget -O- get.pharo.org | bash fi ./pharo Pharo.image save $IMAGE_BASE ./pharo $IMAGE config http://smalltalkhub.com/mc/JanVrany/CalipeL-S/main ConfigurationOfCalipeLS --install=0.1 ./pharo $IMAGE benchmark --json -o results.json BenchmarkMicro === System is running stock 32bit debian stable on VMWare ESX 5.1. I can provide more details if you like (and ask what exactly :-) Best, Jan

June 21, 2013