June 2013 - Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] [Ann] VMMaker + Cog building in Pharo20

by HernÃ¡n Morales Durand

Great but next time check better because I did these changes 2 months ago and nobody asked: http://comments.gmane.org/gmane.comp.lang.smalltalk.squeak.vm.devel/10184 HernÃ¡n El 19/06/2013 6:08, Guillermo Polito escribiÃ³: > So, I finished committing and made a last smoke test. VMMaker loads in > Pharo2.0 and uses (mostly) Filesystem. I used the rewriting engine to > rewrite some parts, and some others I made manually... > > To sum up: > - I created a new version in configuration of cog: 6.5 (in the way I > touched ConfigurationOfAsmJit for those related...) > - I uploaded this configuration to old MetacelloRepository and > MetaRepoForPharo20 in ss3. So you can use either of these: > > Gofer it > squeaksource: 'MetacelloRepository'; > configurationOf: 'Cog'; > load. > > Gofer it > squeaksource3: 'MetaRepoForPharo20'; > configurationOf: 'Cog'; > load. > > - Version 6.5 is intended to be used in Pharo 2.0. > > (ConfigurationOfCog project version: '6.5') load. > > - I tested building a pharo vm and a simple cog, *only in mac*. So, > further testing is needed :) But it's a start. > > PharoVMBuilder buildMacOSX32. > > CogCocoaIOSConfig new > generateForRelease; > addExternalPlugins: #( FT2Plugin ); > addInternalPlugins: #( UnixOSProcessPlugin ); > "addThirdpartyLibrary: 'cairo';" > generateSources; generate. > > > So a next step is to update the gitorious scripts to use pharo 2.0 + cog > 6.5 instead of pharo 1.4 + cog 6.4. > > And we probably have to review the numbering inside ConfigurationOfCog :). > > Guille

June 21, 2013

[update 3.0] #30215

by Esteban Lorenzano

30215 ----- 10976 kernel methods refactor https://pharo.fogbugz.com/f/cases/10976/kernel-methods-refactor (pass 6, last?) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Traits-EstebanLorenzano.514.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Ring-Core-Kernel-EstebanLoren… http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Core-EstebanLorenzan… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-EstebanLorenzano.478… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Manifest-Core-EstebanLorenzan… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-EstebanLorenzano.1491.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-EstebanLorenzano.489…

June 21, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 1 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods

June 21, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. KernelTests.Classes.ClassDescriptionTest.testUnCategorizedMethods

June 21, 2013