- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 18:03, Adrian Lienhard wrote: > IIRC Marcus introduced Behavior>>hash in 3.9 and later realized that > this is not a good idea. The reason is that names of behaviors are > not constant because when a class is deleted its name is changed to > AnAbsolete..., which makes the name not suitable for hashing. > Yes, that was the reason. > Looking through ScriptLoader, #update10020 is where Behavior>>hash > is removed again. Unfortunately the changes log is a bit unspecific > as it mentions only: "changes from Reflectivity"... > I will try to be more specific next time... > Cheers, > Adrian > > On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: > >> >> What was his fix? >> >> How can I tell what was changed? >> >> Is Behaviour>>hash missing in your image too? I don't trust >> anything anymore. >> >> - on >> >> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >> >>> Marcus should have a look since this is fix he reverted. >>> >>> Stef >>> >>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> These tests are fine in Squeak 3.9 too. >>>> >>>> Further investigation reveals that Behaviour>>hash is missing in >>>> Pharo! >>>> >>>> So hash reverts to Object>>hash, which sends Object>>identityHash. >>>> >>>> In Pharo: >>>> >>>> Array hash --> 2455 >>>> Object identityHash --> 2274 >>>> >>>> In Squeak: >>>> >>>> Array hash --> 259007228 >>>> Object identityHash --> 2274 >>>> >>>> Looks like someone removed >>>> >>>> Behaviour>>hash >>>> ^ self name hash >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Excellent! >>>>> may be this is the hash of class that changed. Marcus >>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>> And may be in 3.10 they changed class hash too. >>>>> >>>>> Now I do not know if in 3.9 these tests were broken. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> OK, I investigated more deeply. >>>>>> >>>>>> It appears that SequenceableCollection>>hash behaves >>>>>> differently in Pharo and Squeak 3.10. >>>>>> >>>>>> Squeak: >>>>>> >>>>>> #(1) hash --> 22516953 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> #(1) hash --> 61541560 >>>>>> >>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>> Array>>hash (inherited from SequenceableCollection), this test >>>>>> fails. >>>>>> >>>>>> Not yet sure why these two behave differently ... >>>>>> >>>>>> Already the first line (self species hash) is different: >>>>>> >>>>>> Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> We checked with lukas what is strange is that the same tests >>>>>>> are green in 3.10. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>> Number tests run, and in the Issues page I propose to delete >>>>>>>> a bunch of nonsensical testHash tests. With these changes >>>>>>>> the Kernel tests should all be green. >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pharo-project mailing list >>>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 19:11, StÃ©phane Ducasse wrote: > Yes I have the impression that this would be a good things to do > because > they do not have add that much important information. > > Yes, that is my impression too. > On Jun 11, 2008, at 6:11 PM, Oscar Nierstrasz wrote: > >> >> OK, so that is why all these silly testHash tests are broken. They >> depend on Behaviour>>#hash to return a specific hash value. I >> suggest trashing them as the tests are not robust. >> >> - on >> >> >> On Jun 11, 2008, at 6:03 PM, Adrian Lienhard wrote: >> >>> IIRC Marcus introduced Behavior>>hash in 3.9 and later realized >>> that this is not a good idea. The reason is that names of >>> behaviors are not constant because when a class is deleted its >>> name is changed to AnAbsolete..., which makes the name not >>> suitable for hashing. >>> >>> Looking through ScriptLoader, #update10020 is where Behavior>>hash >>> is removed again. Unfortunately the changes log is a bit >>> unspecific as it mentions only: "changes from Reflectivity"... >>> >>> Cheers, >>> Adrian >>> >>> On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: >>> >>>> >>>> What was his fix? >>>> >>>> How can I tell what was changed? >>>> >>>> Is Behaviour>>hash missing in your image too? I don't trust >>>> anything anymore. >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Marcus should have a look since this is fix he reverted. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> These tests are fine in Squeak 3.9 too. >>>>>> >>>>>> Further investigation reveals that Behaviour>>hash is missing >>>>>> in Pharo! >>>>>> >>>>>> So hash reverts to Object>>hash, which sends >>>>>> Object>>identityHash. >>>>>> >>>>>> In Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> In Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> Looks like someone removed >>>>>> >>>>>> Behaviour>>hash >>>>>> ^ self name hash >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Excellent! >>>>>>> may be this is the hash of class that changed. Marcus >>>>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>>>> And may be in 3.10 they changed class hash too. >>>>>>> >>>>>>> Now I do not know if in 3.9 these tests were broken. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> OK, I investigated more deeply. >>>>>>>> >>>>>>>> It appears that SequenceableCollection>>hash behaves >>>>>>>> differently in Pharo and Squeak 3.10. >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> #(1) hash --> 22516953 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> #(1) hash --> 61541560 >>>>>>>> >>>>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>>>> Array>>hash (inherited from SequenceableCollection), this >>>>>>>> test fails. >>>>>>>> >>>>>>>> Not yet sure why these two behave differently ... >>>>>>>> >>>>>>>> Already the first line (self species hash) is different: >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> Array hash --> 259007228 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> Array hash --> 2455 >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>>>> >>>>>>>>> We checked with lukas what is strange is that the same tests >>>>>>>>> are green in 3.10. >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>>>> Number tests run, and in the Issues page I propose to >>>>>>>>>> delete a bunch of nonsensical testHash tests. With these >>>>>>>>>> changes the Kernel tests should all be green. >>>>>>>>>> >>>>>>>>>> - on >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Pharo-project mailing list >>>>>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Pharo-project mailing list >>>>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Pharo-project mailing list >>>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- >>>>> project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > > [snip] > >> Is is politically really important that we use the inria infrastructure. > >> It will help us building Smalltalk presence inside INRIA. > >> So at then end we will not use the forge but only the file because we need > >> these counters > >> at that place :) > > > > Fair enough. I have disabled the "Downloads" tab in googlecode. > > I thought things better and just turned the "Downloads" tab into a > wiki page to redirect people to the right place. > > BTW, PharoReady.cs is not available. Stephane, could you please add it? > I added it. I've put it into the svn and linked it from there. I don't think the initial cs has be add inria. Norbert > Thanks, > > Victor. > > > > VÃctor. > > > >>> I will volunteer again and move all the existing files over. (As a > >>> matter of fact, I had been thinking of moving the files then proposing > >>> the change, but I just haven't had a chance to do it.) > >> > >> Please don't there are issues more complex under the surface but this is not > >> linked with pharo by itself. > >> > >>> > >>> > >>> Victor. > >>> > >>> > >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >>>> > >>>>> > >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >>>>> "pharo-dev" on the downloads page. > >>>>> > >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >>>>> > >>>>> - on > >>>>> > >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >>>>> > >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >>>>>> wrote: > >>>>>>> > >>>>>>> Great! > >>>>>>> > >>>>>>> Just noticed two things: > >>>>>>> > >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >>>>>> > >>>>>> > >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >>>>>> you want a prepared pharo image for developers. > >>>>>> > >>>>>> -- > >>>>>> Damien Cassou > >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Pharo-project mailing list > >>>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Pharo-project mailing list > >>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

[Pharo-project] Fwd: Comment on BrokenTests in pharo

by Pharo Smalltalk

My apologies if this message is forwarded to the list twice. Victor Rodriguez. ---------- Forwarded message ---------- From: <codesite-noreply(a)google.com> Date: Wed, Jun 11, 2008 at 12:05 PM Subject: Comment on BrokenTests in pharo To: pharo.smalltalk(a)gmail.com Comment by oscar.nierstrasz: FloatTests>>#testNaN5 currently reads as follows: {{{ testNaN5 "self assert: (Float nan asIEEE32BitWord printPaddedWith: $0 to: 32 base: 2) = '01111111110000000000000000000000'." ... }}} I believe this is over-specified. Instead it should just read as follows: {{{ testNaN5 self assert: ((Float nan asIEEE32BitWord printPaddedWith: $0 to: 32 base: 2) copyFrom: 2 to: 9) = '11111111'. ... }}} This would be consistent with the NaN spec (according to wikipedia). However it does not explain why these tests pass in 3.9 and 3.10. Have there been changes in the VM to the way that Floats are represented? For more information: http://code.google.com/p/pharo/wiki/BrokenTests

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Victor Rodriguez

On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > [snip] >> Is is politically really important that we use the inria infrastructure. >> It will help us building Smalltalk presence inside INRIA. >> So at then end we will not use the forge but only the file because we need >> these counters >> at that place :) > > Fair enough. I have disabled the "Downloads" tab in googlecode. I thought things better and just turned the "Downloads" tab into a wiki page to redirect people to the right place. BTW, PharoReady.cs is not available. Stephane, could you please add it? Thanks, Victor. > VÃctor. > >>> I will volunteer again and move all the existing files over. (As a >>> matter of fact, I had been thinking of moving the files then proposing >>> the change, but I just haven't had a chance to do it.) >> >> Please don't there are issues more complex under the surface but this is not >> linked with pharo by itself. >> >>> >>> >>> Victor. >>> >>> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: >>>> >>>>> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under >>>>> "pharo-dev" on the downloads page. >>>>> >>>>> http://gforge.inria.fr/frs/?group_id=1299 >>>>> >>>>> - on >>>>> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: >>>>> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>>>>> wrote: >>>>>>> >>>>>>> Great! >>>>>>> >>>>>>> Just noticed two things: >>>>>>> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? >>>>>> >>>>>> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if >>>>>> you want a prepared pharo image for developers. >>>>>> >>>>>> -- >>>>>> Damien Cassou >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Victor Rodriguez

On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: [snip] > Is is politically really important that we use the inria infrastructure. > It will help us building Smalltalk presence inside INRIA. > So at then end we will not use the forge but only the file because we need > these counters > at that place :) Fair enough. I have disabled the "Downloads" tab in googlecode. VÃctor. >> I will volunteer again and move all the existing files over. (As a >> matter of fact, I had been thinking of moving the files then proposing >> the change, but I just haven't had a chance to do it.) > > Please don't there are issues more complex under the surface but this is not > linked with pharo by itself. > >> >> >> Victor. >> >> >>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> Ah, I thought it *was* a pharo-dev image -- it was listed under >>>> "pharo-dev" on the downloads page. >>>> >>>> http://gforge.inria.fr/frs/?group_id=1299 >>>> >>>> - on >>>> >>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: >>>> >>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> >>>>> wrote: >>>>>> >>>>>> Great! >>>>>> >>>>>> Just noticed two things: >>>>>> >>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? >>>>> >>>>> >>>>> I think Pharo should not care about such things. Just use pharo-dev if >>>>> you want a prepared pharo image for developers. >>>>> >>>>> -- >>>>> Damien Cassou >>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Victor Rodriguez

On Wed, Jun 11, 2008 at 5:08 PM, Norbert Hartl <norbert(a)hartl.name> wrote: [snip] > Yes, I'll open a ticket. I think we are using google. So after all > we use: > > - google for wiki and bugs > - inria for file downloads > - squeaksource for code upload - inria for the mailing list. VÃctor. > > we seem not to use: > > - bugs.squeak.org (we should someone remove the project from there) > > Norbert >> I will ask samuel if he has some ideas for the logo because we should >> move on >> for the infrastructure of the web site (I'm sorry about the current >> state of affair). >> >> >> On Jun 11, 2008, at 7:43 PM, Norbert Hartl wrote: >> >> > Hmmm, it has something to do with the name pharo :) I checked >> > the available images. Sapphire 10018 doesn't show up this. But >> > Pharo 10021 does. And in 10021 there is one additional test in >> > ClassTest >> > >> > testHaSharedPools >> > >> > Author seems to be Stephane. Do you know anything which have >> > introduced this? >> > >> > Norbert >> > >> > >> > On Wed, 2008-06-11 at 19:24 +0200, Norbert Hartl wrote: >> >> If you open a test runner and select only KernelTests-ClassTest and >> >> TraitsTests-TraitsTestCase you may find a failure >> >> >> >> ClassTest>>testRootsOfTheWorld >> >> >> >> But I don't understand fully why it appears. I had once >> >> the chance to get a debugger on the failure (which does >> >> usually not work on this failure) and so I know that the >> >> rootsOfTheWorld (which is usually 3) is 6 in size containing >> >> additionally classes C3 C4 and C6. The ones which are created >> >> by TraitsTestCase (see my last mail "Bug for harvest"). >> >> >> >> They all have a superclass of nil but they aren't included >> >> in the SystemNavigation. (conditions for being included in >> >> the rootsOfTheWorld) >> >> >> >> If you press "Run selected" again the same error occurrs >> >> while pressing "Run failures" gives you all green (ok, it >> >> is this way in my case) >> >> >> >> And I can't reproduce the same in a 3.10 image. >> >> >> >> It seems that there is a timing problem involved. Selecting >> >> only the two test cases I get the failure every time (or nearly). >> >> Selecting all tests it appears only at random. >> >> >> >> Any hints? >> >> >> >> Norbert >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by Victor Rodriguez

On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> wrote: [snip] > What would you prefer? > > 1. Opening issues where they belong first and let "the others" > harvest what they think they need? > 2. Playing back the issues to bugs.squeak.org if we find a bug > that belongs also to squeak and bring them back by harvesting? This is what I propose: * If an issue applies to Squeak, file a report on Mantis. > How do we want to harvest fixes from other places? > > 1. Having a wiki page where issues found are written down? > 2. Opening tickets on the google tracker for this? This would > be "to harvest" tickets. * File an issue for everything we want to do in Pharo in the google tracker, *including* for "harvesting" fixes in other projects. Thus, I would still file an issue on the google tracker for Mantis reports. Such issues should probably follow a template, and have a label that indicates their origin (in addition to the description). As a matter of fact, I think we should file an issue for every fix listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, etc.. This way, people can assign to themselves a given fix, and we can more easily keep a handle on things. The issue tracker should be the *one* place where you can find what nees to be done. BTW, this leads to something else I wanted to bring up. Currently, "harvest" means two things: 1) Put in Pharo a fix available in Squeak (or Croquet, etc..); and 2) Move a package from the PharoInbox into the Pharo update stream. Could we come up with a different name for 2? Something along the lines of 'integrate', 'validate', 'process', etc.. "Stephane is processing fix X in the PharoInbox". Saludos, VÃctor RodrÃguez. > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

[Pharo-project] Pharo, squeak and the tickets

by Norbert Hartl

I had a look at the tickets in the google tracker. A lot of them appear to me that they belong to squeak as well. I'm quite unsure what would be the best way to deal with both sides (pharo and squeak) because there are bugs found through working on pharo that belong to squeak as well. On the other hand we harvest things from squeak. What would you prefer? 1. Opening issues where they belong first and let "the others" harvest what they think they need? 2. Playing back the issues to bugs.squeak.org if we find a bug that belongs also to squeak and bring them back by harvesting? How do we want to harvest fixes from other places? 1. Having a wiki page where issues found are written down? 2. Opening tickets on the google tracker for this? This would be "to harvest" tickets. Norbert

June 11, 2008

Re: [Pharo-project] Bug for harvesting

by Serge Stinckwich

2008/6/11 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-06-11 at 14:50 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> wrote: >> > Hi, >> > >> > I opened a bug a few minutes ago which you may find interesting >> > for harvest. >> > >> > http://bugs.squeak.org/view.php?id=7090 >> >> I have filed this as Issue 13. I left the state as NEW. >> > I don't think it is good to open tickets in two different bug > trackers. I opened it on squeak.org because it is a defect that > doesn't belong to pharo. Things get messed quickly this way. > There is a wiki page MantisBugsHarvested. Why shouldn't we have > another page for bugs supposed to be harvested. They exist for > 3.10 already. > > Norbert > > P.S.: I cannot create pages in the wiki. Can someone add me, please! > The account is my email address. I add you. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 11, 2008