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

Re: [Pharo-dev] failing moose tests

by Stephan Eggermont

There has been a fixed package on smalltalkhub since 10 days, so it looks like a configuration problem Name: Moose-Test-HismoImporter-StephanEggermont.5 Author: StephanEggermont Time: 20 September 2013, 2:45:53.012 pm UUID: 766c5b47-daa6-4b51-af8f-091539186c59 Ancestors: Moose-Test-HismoImporter-AndreHora.4 Fixed some tests

Sept. 30, 2013

Weird issue with removing instance vars from class def: instance vars jumbled

by phil＠highoctane.be

I guess this has happened to other people. In Pharo 20 and while using Seaside, I was adding, removing , changing components which were making a component and it happened that if I had, let say: a b c d e f turned into a c f Well, c kind of pointed to a b in existing instances and f to old c etc; No matter how much I unregister and reregisted my app, this continued. I got out of the problem by filing out the code and filing it in back, which recomplied the whole component. Weird. I can understand that some existing bytecode wasn't updated when rearranging instvars but for someone new to the game, this would really be weird. Clues? Phil

Sept. 30, 2013

Re: [Pharo-dev] failing moose tests

by Stephan Eggermont

>>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery15Days 64 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery2Years 52 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery6Months 51 ms 3 Don't know where they come from. The implementation should be using everyNDays/Months/Years AFAIK Stephan

Sept. 30, 2013

failing moose tests

by Camillo Bruni

For the vm release tests, we run all the moose tests but there are 3 that constantly fail: https://ci.inria.fr/pharo/view/3.0-VM/job/PharoVM-AcceptanceTest/SLAVE=rmod… >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery15Days 64 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery2Years 52 ms 3 >>> Moose.Test.HismoImporter.MooseHismoImporterTest.testEvery6Months 51 ms 3 All of them fail with the same symptoms: MooseHismoImporter(Object)>>doesNotUnderstand: #every15Days MooseHismoImporterTest>>testEvery15Days MooseHismoImporterTest(TestCase)>>performTest Any clue? ------------------------------------------------------------------------------ REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main ./pharo Pharo.image save Moose ./pharo Moose.image config $REPO ConfigurationOfMoose --install=stable ./pharo Moose.image mooseimagesetup ./pharo Moose.image test --junit-xml-output "Moose.*" ------------------------------------------------------------------------------

Sept. 30, 2013

Re: [Pharo-dev] Primitives lookupEntryIn:index: fails on mac with the latest vm

by Andrei Chis

Might be something related to my particular machine but it happens consistently. I'll try it tomorrow other laptops. On Mon, Sep 30, 2013 at 10:37 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > That would be strange (but only related to the image) since the acceptance > tests almost > pass... > > > https://ci.inria.fr/pharo/view/3.0-VM/job/PharoVM-AcceptanceTest/SLAVE=rmod… > > > > > On 2013-09-30, at 17:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > Ok I will try tomorrow with the latest. > > > > Stef > > > > On Sep 30, 2013, at 10:24 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: > > > >> You have the standard vm installed. I my case I get: > >> > >> 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 > >> NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 > >> https://github.com/pharo-project/pharo-vm.git Commit: > 8252469192542b1adb17185e2d17178e08888903 Date: 2013-09-30 09:44:35 -0300 > By: Camillo Bruni <camillobruni(a)gmail.com> Jenkins build #14724 > >> ' > >> > >> On Mon, Sep 30, 2013 at 10:17 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Hi andrei > >> > >> I never saw it and I could not reproduce it I tried 20 times on > NB-win32 with the latest image and my vm is > >> > >> Smalltalk vm version > >> > >> 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > >> NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > >> git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > >> ' > >> > >> Stef > >> > >>> Hi, > >>> > >>> I was trying to merge a slice into the latest Pharo 3 image when I got > a FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This > happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The > bad part is that it goes into an infinite loop and blocks the image. The > same scenario works ok with the stable pharo vm. > >>> > >>> I can reproduce this by going to the PharoInbox choosing a package > that is not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit > merge. If no error appears the first time, close the merge window and > select merge again. For almost all packages, after a few time I get the > previous error. > >>> > >>> Has anyone encountered this before? Might it be related to > https://pharo.fogbugz.com/f/cases/7559 ? > >>> > >>> Cheers, > >>> Andrei > >> > >> > > > >

Sept. 30, 2013

Re: [Pharo-dev] Primitives lookupEntryIn:index: fails on mac with the latest vm

by Camillo Bruni

That would be strange (but only related to the image) since the acceptance tests almost pass... https://ci.inria.fr/pharo/view/3.0-VM/job/PharoVM-AcceptanceTest/SLAVE=rmod… On 2013-09-30, at 17:33, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok I will try tomorrow with the latest. > > Stef > > On Sep 30, 2013, at 10:24 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> You have the standard vm installed. I my case I get: >> >> 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 >> NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 >> https://github.com/pharo-project/pharo-vm.git Commit: 8252469192542b1adb17185e2d17178e08888903 Date: 2013-09-30 09:44:35 -0300 By: Camillo Bruni <camillobruni(a)gmail.com> Jenkins build #14724 >> ' >> >> On Mon, Sep 30, 2013 at 10:17 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi andrei >> >> I never saw it and I could not reproduce it I tried 20 times on NB-win32 with the latest image and my vm is >> >> Smalltalk vm version >> >> 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 >> NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 >> git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 >> ' >> >> Stef >> >>> Hi, >>> >>> I was trying to merge a slice into the latest Pharo 3 image when I got a FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The bad part is that it goes into an infinite loop and blocks the image. The same scenario works ok with the stable pharo vm. >>> >>> I can reproduce this by going to the PharoInbox choosing a package that is not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit merge. If no error appears the first time, close the merge window and select merge again. For almost all packages, after a few time I get the previous error. >>> >>> Has anyone encountered this before? Might it be related to https://pharo.fogbugz.com/f/cases/7559 ? >>> >>> Cheers, >>> Andrei >> >> >

Sept. 30, 2013

Re: [Pharo-dev] Primitives lookupEntryIn:index: fails on mac with the latest vm

by StÃ©phane Ducasse

Ok I will try tomorrow with the latest. Stef On Sep 30, 2013, at 10:24 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > You have the standard vm installed. I my case I get: > > 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 > https://github.com/pharo-project/pharo-vm.git Commit: 8252469192542b1adb17185e2d17178e08888903 Date: 2013-09-30 09:44:35 -0300 By: Camillo Bruni <camillobruni(a)gmail.com> Jenkins build #14724 > ' > > On Mon, Sep 30, 2013 at 10:17 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi andrei > > I never saw it and I could not reproduce it I tried 20 times on NB-win32 with the latest image and my vm is > > Smalltalk vm version > > 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > git://gitorious.org/cogvm/blessed.git Commit: 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > ' > > Stef > >> Hi, >> >> I was trying to merge a slice into the latest Pharo 3 image when I got a FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The bad part is that it goes into an infinite loop and blocks the image. The same scenario works ok with the stable pharo vm. >> >> I can reproduce this by going to the PharoInbox choosing a package that is not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit merge. If no error appears the first time, close the merge window and select merge again. For almost all packages, after a few time I get the previous error. >> >> Has anyone encountered this before? Might it be related to https://pharo.fogbugz.com/f/cases/7559 ? >> >> Cheers, >> Andrei > >

Sept. 30, 2013

Re: [Pharo-dev] Primitives lookupEntryIn:index: fails on mac with the latest vm

by Andrei Chis

You have the standard vm installed. I my case I get: 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Sep 30 2013 https://github.com/pharo-project/pharo-vm.git Commit: 8252469192542b1adb17185e2d17178e08888903 Date: 2013-09-30 09:44:35 -0300 By: Camillo Bruni <camillobruni(a)gmail.com> Jenkins build #14724 ' On Mon, Sep 30, 2013 at 10:17 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi andrei > > I never saw it and I could not reproduce it I tried 20 times on NB-win32 > with the latest image and my vm is > > Smalltalk vm version > > 'NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > ' > > Stef > > Hi, > > I was trying to merge a slice into the latest Pharo 3 image when I got a > FileSystemError in MacStore(DiskStore)>>basicEntry:path:nodesDo:. This > happens as 'Primitives lookupEntryIn:index:' returns #badDirectoryPath. The > bad part is that it goes into an infinite loop and blocks the image. The > same scenario works ok with the stable pharo vm. > > I can reproduce this by going to the PharoInbox choosing a package that is > not merged (let's say NativeBoost-Win32-CamilloBruni.42) and hit merge. If > no error appears the first time, close the merge window and select merge > again. For almost all packages, after a few time I get the previous error. > > Has anyone encountered this before? Might it be related to > https://pharo.fogbugz.com/f/cases/7559 ? > > Cheers, > Andrei > > >

Sept. 30, 2013

Re: [Pharo-dev] State of SVG importer

by Igor Stasenko

On 30 September 2013 22:08, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> Ok I will update the stable setting because it was just loading the >> development version so breaking the point of stable >> Igor such information should not be only in your head!!!! >> >> > it is work to do.. > but i am not sure it is worth doing. Pharo 2.0 officially not supported by > Athens, so why we should worry about staying compatible? > Yes, in perfect case , configuration baseline should contain branch to > load different versions for 2.0 image, and for 3.0. > > But to do that , first i need to learn (again) how to do it :) > We certainly need a UI tool for configurations, because keeping all those > "how to-s" in head > becomes tedious and counterproductive task. > > > yes and it is coming, versioner will help us for that. > But to me it looks like you did not write enough configurations. I hate > writing them but I do not it because there is no other ways to > manage quality and reproducibility. If this is the price to pay, I pay it > because this is what I want. a ONE CLICK loading system. > I take a reference one and I copy. So now this is done. > > I don't remember, how many of them i wrote, but certainly not enough to remember all things. Most of projects is simple, just plain dependencies, but when things get more complicated like loading different versions for different platform.. this is where usually you need to open manual and read it over again :) > Have a look and see if it loads what you think it should. > > Ok. > Stef > > -- Best regards, Igor Stasenko.

Sept. 30, 2013

[update 3.0] #30434

by Marcus Denker

30434 ----- 7130 Scrollbars on the left. Nobody needed it for years --> remove https://pharo.fogbugz.com/f/cases/7130 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1283.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.130…

Sept. 30, 2013