- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SmallLint applied on Pharo: Continued

by StÃ©phane Ducasse

Thanks! On Jan 24, 2013, at 7:48 AM, Jan Vrany wrote: > Hi, > > we've made all SmallLint code in Smalltalk/X MIT-licensed. > Enjoy. > > Jan > > > On 22/01/13 23:59, StÃ©phane Ducasse wrote: >>> Well. I've written the tag support, so let's make it simple, MIT. >>> I may export a changeset with that code for you, if you like. >> >> Else I will just go over them and it will help me to understand. I think that this is not difficult. >> >>> For rules written by CG I'm not sure. You should check with him. >>> But I think it won't be a problem given that you preserve all >>> the signatures and #documentation and #version_XXX methods >>> (we use them to track changes in the source). >>> >>> However, what I planned (and run out of time :-) is to make >>> tag a first class object with name (symbol) description etc >>> and have class methods to create them. Then one may define and >>> describe meaning of the tag in an extension method. >>> Also, the selection/rejection logic could dispatch back on >>> the tag instance so you may then create fancy dynamic tags >>> (like #portability that automatically includes everything tagged >>> as #pharo #squeak #stx #va, for instance or whatever. >>> >>> I might hack it later this week, if you would include it into >>> your version (otherwise I've more important things to do :-) >> >> I imagine well. >> Let us keep it simple. Simple tags with a little class comments are good enough :) >> >>> >>> Cheers >>> >>> On 22/01/13 19:32, StÃ©phane Ducasse wrote: >>>> Jan >>>> what is the license of your tags and other code? >>>> >>>> Stef >>>> >>>> On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote: >>>> >>>>> On 22/01/13 18:22, StÃ©phane Ducasse wrote: >>>>>> Hi >>>>>> >>>>>> I'm running the rule RBSubclassResponsibilityNotDefinedRule that >>>>>> >>>>>> Checks that all subclassResponsibility methods are defined in all leaf classes. >>>>>> >>>>>> Now the results display the sender of ^ subclassResponsibility but I have to manually find the >>>>>> problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method. >>>>>> >>>>>> But this would be much better. Jan did you do that in your version? >>>>> >>>>> Good point. Yes, since now we do that :-) >>>>> >>>>> Jan >>>>> >>>>>> >>>>>> Stef >>>>>> >>>>> >>>>> >>>> >>>> >>>> >>> >>> >> >> >> > > <smalltalkx-lint.zip>

Jan. 24, 2013

Re: [Pharo-project] pharotaskforces broken on squeaksource

by StÃ©phane Ducasse

Ok I published a new version of the fix and let me know. Indeed removing the file physically would be good too. I do not have access to it. Stef > Indeed, I thought of that, too. But, the problem is that the web interface only shows one single package versions, probably because after the restart the index in the image was not updated. > > In any case, my original question was why do we have a ".mcz" file at all? But, I will look into the fix of Stef. And, tomorrow I will go to SCG and see if we can actually remove the offending file from the file system. > > Cheers, > Doru > > > On Jan 24, 2013, at 2:14 AM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Tudor Girba-2 wrote >>> Or how to fix this? >> >> The immediate problem can be fixed by deleting the version on sqs, no? >> Requires admin access i.e. StÃ©phane Ducasse, Alexandre Bergel, Marcus >> Denker, Alain Plantec >> >> >> >> -- >> View this message in context: http://forum.world.st/pharotaskforces-broken-on-squeaksource-tp4664764p4665… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- > www.tudorgirba.com > > "Every thing has its own flow." > > > > >

Jan. 24, 2013

Re: [Pharo-project] looking for the description of the MC file package format convention

by StÃ©phane Ducasse

Jan. 24, 2013

Re: [Pharo-project] Image size of 2.0...

by Sean P. DeNigris

Marcus Denker-4 wrote > The download of 2.0 now has ca. 30MB, which is large. > > But... 15.4MB I am in awe that I can download the closest thing the world has ever come to dynabook software in 20 seconds on my home internet. This is truly an exciting time to be alive!! Cheers, Sean p.s. 10 seconds for 15MB is even nicer... what will I do with the time ;) -- View this message in context: http://forum.world.st/Image-size-of-2-0-tp4665128p4665172.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 24, 2013

Re: [Pharo-project] destructive / regression tests

by Marcus Denker

On Jan 24, 2013, at 6:16 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> I've been thinking these days on how to implement regression tests. >> Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. >> >> For now I will put them into a separate repository: >> >> http://smalltalkhub.com/#!/~Pharo/regression-testing >> >> Some question: >> - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? >> - Is it ok to rely on OSProcess for now to run launch a separate new image? > > + 1 > we need such tests. > And actually it would be even useful to know which code crashing the > system , e.g. > we can even have a tests which succeed only if they crashing VM. Yes! We did a first (ad-hoc) regression tester for Opal: https://ci.inria.fr/rmod/job/OpalRegression/ We just have the tests in different packages and take care which to run when. The regression-test job runs first slow tests that can not do any harm (compiling all method, but not installing them), then as a second to run tests that recompile the whole image, this we save and then run all tests on that: ./vm.sh $JOB_NAME.image test --junit-xml-output "OpalCompiler-RegressionTests.*" ./vm.sh $JOB_NAME.image test --junit-xml-output "OpalCompiler-DestructiveRegressionTests.*" --save ./vm.sh $JOB_NAME.image test --junit-xml-output ".*" With that in place we can be quire sure that a change done on the compiler is not doing anything wrong. (and that speeds up development quite a lotâ¦) Marcus

Jan. 24, 2013

Re: [Pharo-project] Image size of 2.0...

by Camillo Bruni

that's nice cause the whole information for Monticello and the ScriptLoader could be retrieved online on demand! On 2013-01-24, at 16:09, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > With Esteban we checked a bit image size. > > The download of 2.0 now has ca. 30MB, which is large. > > But: > > -> Delete Monticello history > -> Unload Scroptloader > -> do #cleanUpForRelease > > Result: 15.4MB, with all tests, NativeBoost, RB... > > This is not too bad! > > Marcus >

Jan. 24, 2013

Re: [Pharo-project] destructive / regression tests

by Camillo Bruni

On 2013-01-24, at 18:16, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> I've been thinking these days on how to implement regression tests. >> Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. >> >> For now I will put them into a separate repository: >> >> http://smalltalkhub.com/#!/~Pharo/regression-testing >> >> Some question: >> - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? >> - Is it ok to rely on OSProcess for now to run launch a separate new image? > > + 1 > we need such tests. > And actually it would be even useful to know which code crashing the > system , e.g. > we can even have a tests which succeed only if they crashing VM. yes exactly!! I even thought about doing this random code-change validation ;) 1. chose a random method (minus some uninteresting packages or only those with methods) 2. make it return a wrong value 3. run all tests 4. make sure we get an assertion failed ;)

Jan. 24, 2013

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

by Esteban Lorenzano

nope... HD package is still using PackageInfo, that's the problem... I will review it tomorrow On Jan 24, 2013, at 6:13 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > so was it an RPackage bug? or a CLI-TestRunner / HDReport problem? > > On 2013-01-24, at 18:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> looks like there are still some duplicates :( >> >> On Jan 24, 2013, at 6:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. >>> >>> On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> what was caused the issue with the jenkins tests? >>>> >>>> On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>>> 20486 >>>>> ----- >>>>> >>>>> Issue 7316: Jenkins: Some tests are run twice >>>>> http://code.google.com/p/pharo/issues/detail?id=7316 >>>>> >>>>> Issue 6861: cmd+w is broken for explore browser >>>>> http://code.google.com/p/pharo/issues/detail?id=6861 >>>>> >>>>> Issue 7313: MCWorkingCopy querying facilities... >>>>> http://code.google.com/p/pharo/issues/detail?id=7313 >>>>> >>>>> Diff information: >>>>> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >>>>> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >>>>> >>>>> >>>> >>>> >>> >> >> > >

Jan. 24, 2013

Re: [Pharo-project] destructive / regression tests

by Igor Stasenko

On 24 January 2013 18:12, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I've been thinking these days on how to implement regression tests. > Obviously the core requirement is to launch a separate image and capture terminal output and/or result files. > > For now I will put them into a separate repository: > > http://smalltalkhub.com/#!/~Pharo/regression-testing > > Some question: > - Is there a test ConfigurationOf* which can be used to try loading different versions / groups? > - Is it ok to rely on OSProcess for now to run launch a separate new image? + 1 we need such tests. And actually it would be even useful to know which code crashing the system , e.g. we can even have a tests which succeed only if they crashing VM. -- Best regards, Igor Stasenko.

Jan. 24, 2013

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

by Camillo Bruni

so was it an RPackage bug? or a CLI-TestRunner / HDReport problem? On 2013-01-24, at 18:09, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > looks like there are still some duplicates :( > > On Jan 24, 2013, at 6:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> package test was taking all packages, even all those who does not have any class defined, but are "super-packages"... that's why some tests where ran twice. >> >> On Jan 24, 2013, at 5:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> what was caused the issue with the jenkins tests? >>> >>> On 2013-01-24, at 17:57, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> 20486 >>>> ----- >>>> >>>> Issue 7316: Jenkins: Some tests are run twice >>>> http://code.google.com/p/pharo/issues/detail?id=7316 >>>> >>>> Issue 6861: cmd+w is broken for explore browser >>>> http://code.google.com/p/pharo/issues/detail?id=6861 >>>> >>>> Issue 7313: MCWorkingCopy querying facilities... >>>> http://code.google.com/p/pharo/issues/detail?id=7313 >>>> >>>> Diff information: >>>> http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1331.diff >>>> http://ss3.gemstone.com/ss/Pharo20/Monticello-EstebanLorenzano.745.diff >>>> http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-EstebanLorenzano.138.diff >>>> http://ss3.gemstone.com/ss/Pharo20/HudsonBuildTools20-EstebanLorenzano.19.d… >>>> >>>> >>> >>> >> > >

Jan. 24, 2013