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

Re: [Pharo-dev] sunit failures vs errors

by Norbert Hartl

Am 10.07.2013 um 15:33 schrieb Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Oh, so programming in the debugger was a myth? > I'm disappointed ;) > Well, I would say it is neither a myth nor has it to be forced. There is always more than one work mode. So you program only in the debugger? Did you uninstall all browsers, inspectors, etc.? Need to think about that approach! :) Norbert > > 2013/7/10 Damien Cassou <damien.cassou(a)gmail.com> > > On Wed, Jul 10, 2013 at 8:16 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I use them. I always fix the red tests first because they are mostly easier to fix and some of them lead to yellow tests > > I agree with you. I tend to do that as well. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill >

July 10, 2013

Re: [Pharo-dev] sunit failures vs errors

by Nicolas Cellier

Oh, so programming in the debugger was a myth? I'm disappointed ;) 2013/7/10 Damien Cassou <damien.cassou(a)gmail.com> > > On Wed, Jul 10, 2013 at 8:16 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> I use them. I always fix the red tests first because they are mostly >> easier to fix and some of them lead to yellow tests > > > I agree with you. I tend to do that as well. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing > enthusiasm." > Winston Churchill >

July 10, 2013

Re: [Pharo-dev] PhExample repository

by Norbert Hartl

thanks. Can someone add at least a comment on the PharoExtras repo ? thanks, Norbert Am 10.07.2013 um 15:01 schrieb Stefan Marr <smalltalk(a)stefan-marr.de>: > Hi: > > On 10 Jul 2013, at 14:50, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Which one is the right repository? >> http://smalltalkhub.com/#!/~PharoExtras/Phexample >> or >> http://smalltalkhub.com/#!/~Phexample/Phexample > > As far as I remember, Camillo was going to clean that up. The PharoExtras repo was supposed to be deleted, but SmalltalkHub didn't have a delete button back than. > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

July 10, 2013

Re: [Pharo-dev] PhExample repository

by Norbert Hartl

thanks Doru Am 10.07.2013 um 15:01 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > On Jul 10, 2013, at 2:50 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> Which one is the right repository? >> >> http://smalltalkhub.com/#!/~PharoExtras/Phexample >> >> or >> >> http://smalltalkhub.com/#!/~Phexample/Phexample > > This one. > > Doru > >> And if they are copies of each other could you please change one of those to include a comment/pointer that the other one is in use? >> >> Norbert >> > > -- > www.tudorgirba.com > > "One cannot do more than one can do." > > > >

July 10, 2013

Re: [Pharo-dev] Nice VM crash - UPDATE

by Jan Vrany

Hi, a small update to my VM crash. Actually, sometimes it does not crash :-) (see [1] - the VM is the same all the time). My wild guess is some GC related problem, depending on timing and actual memory contents/layout, maybe? Cheers, Jan [1]: https://swing.fit.cvut.cz/jenkins/view/CalipeL/job/calipel_s_pharo20_benchm… On 21/06/13 18:37, Jan Vrany 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

July 10, 2013

Re: [Pharo-dev] UIPainter in need of some help?

by Erwan Douaille

I didn't commit since the past week. I'm trying many things with Spec. Don't worry i'm working on it :) I will pair program with Esteban tomorrow. I didn't receive an answer from Ben about pair programming. And i was going to post a question : *Hi, * * * *I used a DyncamicComposableModel and i include it in a spec model with others spec stuff.* * * *I would like to refresh its content. My first idea was to do the same thing shown in the example : * * * * * * self needRebuild: false.* * self openWithSpecLayout: self layout.* * * *self layout is a layout than i build dynamicly.* *The problem is, my DyncamicComposable.... becomes empty and a new window appears with correct items.* * * *Any clue ? * * * *Thanks :)* Thanks :) 2013/7/10 Stephan Eggermont <stephan(a)stack.nl> > Hi, > > I looked today at the code of UIPainter on Smalltalkhub, > and it looks like Erwan can use some help. > > Stephan > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

July 10, 2013

Re: [Pharo-dev] sunit failures vs errors

by Tudor Girba

Hi, On Jul 10, 2013, at 3:01 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-07-10, at 14:47, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> On Jul 10, 2013, at 1:47 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> On 2013-07-10, at 13:32, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> Precisely. There is a huge difference between invalidating a known contract (i.e., failure) and raising an unexpected error (i.e., error). >>> >>> In which sense? >> >> In the sense that they express two distinct classes of problems. >> >>> As a programmer I have to tackle them both the same way: start debugging. >> >> Yes, but not all debugging is created equal :) >> >>> I really do not see the difference. In both cases the code does not behave as expected. >>> One might even say that there is a global contract that the code does not raise exceptions. >> >> Yes, but then what is the point of explicit assertions? :) >> >>> Tackling the failures first is purely a habit induced by the existing system that errors are worse than failures >> >> Actually, it is the other way around :). Errors are much faster to fix than failures. Errors are often caused by bad initializations and you can see it rather fast when you see the exceptions. On the other hand, failures are often more sensitive to the deep semantics of your code and that is why they require more time to get fixed. > > That is fun, because everybody first takes the yellow ones because they come on top... Really? I think people pick and choose (or at least try to) before fixing a test. So, any hints that help people with this choice is a good thing. This is why the premise of Phexample could bring so much value because besides the fluent interface, it builds a tree of tests. > So in the end the results should just be grouped by type of error I think. That is actually a rather cool idea. I would be happy to join playing with such an idea. Cheers, Doru -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

July 10, 2013

UIPainter in need of some help?

by Stephan Eggermont

Hi, I looked today at the code of UIPainter on Smalltalkhub, and it looks like Erwan can use some help. Stephan

July 10, 2013

Re: [Pharo-dev] sunit failures vs errors

by Camillo Bruni

On 2013-07-10, at 14:47, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > On Jul 10, 2013, at 1:47 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> On 2013-07-10, at 13:32, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Precisely. There is a huge difference between invalidating a known contract (i.e., failure) and raising an unexpected error (i.e., error). >> >> In which sense? > > In the sense that they express two distinct classes of problems. > >> As a programmer I have to tackle them both the same way: start debugging. > > Yes, but not all debugging is created equal :) > >> I really do not see the difference. In both cases the code does not behave as expected. >> One might even say that there is a global contract that the code does not raise exceptions. > > Yes, but then what is the point of explicit assertions? :) > >> Tackling the failures first is purely a habit induced by the existing system that errors are worse than failures > > Actually, it is the other way around :). Errors are much faster to fix than failures. Errors are often caused by bad initializations and you can see it rather fast when you see the exceptions. On the other hand, failures are often more sensitive to the deep semantics of your code and that is why they require more time to get fixed. That is fun, because everybody first takes the yellow ones because they come on top... So in the end the results should just be grouped by type of error I think.

July 10, 2013

Re: [Pharo-dev] PhExample repository

by Stefan Marr

Hi: On 10 Jul 2013, at 14:50, Norbert Hartl <norbert(a)hartl.name> wrote: > Which one is the right repository? > http://smalltalkhub.com/#!/~PharoExtras/Phexample > or > http://smalltalkhub.com/#!/~Phexample/Phexample As far as I remember, Camillo was going to clean that up. The PharoExtras repo was supposed to be deleted, but SmalltalkHub didn't have a delete button back than. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

July 10, 2013