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

Re: [Pharo-project] Socket objects created twice ?

by Sven Van Caekenberghe

OK thanks, Henry. This behavior is then to be expected for all objects registered for finalization I guess. On 12 Jul 2011, at 14:20, Henrik Sperre Johansen wrote: > Didn't really answer these, if it weren't obvious: > On 12.07.2011 13:38, Sven Van Caekenberghe wrote: >> Is there really only one OS level socket ? > Yes, only the one returned from newXYZ gets registered externally. >> Does this have to do with Sockets being in a WeakRegistry ? > > Yes, the other is used to release the externally registered resource when the one you created is no longer referenced (ie. to finalize it) > > Cheers, > Henry >

July 12, 2011

Re: [Pharo-project] Socket objects created twice ?

by Igor Stasenko

As Henrik says, it is normal: for each real socket there two Socket instances. On 12 July 2011 14:20, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > Didn't really answer these, if it weren't obvious: > On 12.07.2011 13:38, Sven Van Caekenberghe wrote: >> >> Is there really only one OS level socket ? > > Yes, only the one returned from newXYZ gets registered externally. >> >> Does this have to do with Sockets being in a WeakRegistry ? > > Yes, the other is used to release the externally registered resource when > the one you created is no longer referenced (ie. to finalize it) > > Cheers, > Henry > > -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-project] Old Hudson still builds?

by Janko MivÅ¡ek

S, Igor Stasenko piÅ¡e: >>>> Is old Hudson still building? I namelly wait for new version of Aida to >>>> be built, but last (and failed) was built 3 days ago... >>> No, currently it just doesn't builds anything. Since your job depends on 1.3 >>> and since there is no updates to 1.3 , it simply not triggers. >>> >>> I could trigger this job if you want. >> >> Yes please. > > it builds now. Thanks a lot! >> And you can open it on new Jenkins for Pharo 1.4 too. >> > yes, give it a time :) > > i'd prefer people to do manage their jobs by own (to have less > pressure on Marcus and me). With pleasure, just give us instructions and access! > > Marcus, can we register new users on Jenkins? > >> Best regards >> Janko >>

July 12, 2011

Re: [Pharo-project] Old Hudson still builds?

by Igor Stasenko

2011/7/12 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: > > > S, Igor Stasenko piÅ¡e: >> 2011/7/12 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: >>> Hi guys, >>> >>> Is old Hudson still building? I namelly wait for new version of Aida to >>> be built, but last (and failed) was built 3 days ago... >>> >> >> No, currently it just doesn't builds anything. Since your job depends on 1.3 >> and since there is no updates to 1.3 , it simply not triggers. >> >> I could trigger this job if you want. > > Yes please. it builds now. > And you can open it on new Jenkins for Pharo 1.4 too. > yes, give it a time :) i'd prefer people to do manage their jobs by own (to have less pressure on Marcus and me). Marcus, can we register new users on Jenkins? > Best regards > Janko > -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-project] Old Hudson still builds?

by Janko MivÅ¡ek

S, Igor Stasenko piÅ¡e: > 2011/7/12 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: >> Hi guys, >> >> Is old Hudson still building? I namelly wait for new version of Aida to >> be built, but last (and failed) was built 3 days ago... >> > > No, currently it just doesn't builds anything. Since your job depends on 1.3 > and since there is no updates to 1.3 , it simply not triggers. > > I could trigger this job if you want. Yes please. And you can open it on new Jenkins for Pharo 1.4 too. Best regards Janko -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

July 12, 2011

Re: [Pharo-project] Old Hudson still builds?

by Igor Stasenko

2011/7/12 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: > Hi guys, > > Is old Hudson still building? I namelly wait for new version of Aida to > be built, but last (and failed) was built 3 days ago... > No, currently it just doesn't builds anything. Since your job depends on 1.3 and since there is no updates to 1.3 , it simply not triggers. Here the error which causing job to fail: + /builds/builder/build.sh -i Full1.3 -s pharo/aida -o Aida build.sh: error loading code (/builds/vm/bin/squeak) THERE_BE_DRAGONS_HERE Error: Could not resolve: Aida63 [Aida63] in /builds/workspace/Aida Pharo 1.3/Aida/package-cache http://www.squeaksource.com/Aida 9 July 2011 10:41:05 pm VM: unix - i686 - linux - Squeak4.1 of 17 April 2010 [latest update: #9957] Image: Pharo1.3 [Latest update: #13285] MetacelloFetchingMCSpecLoader(Object)>>error: Receiver: a MetacelloFetchingMCSpecLoader(linear load : 6.3 [ConfigurationOfAida] linear load : 2.3...etc... Arguments and temporary variables: aString: 'Could not resolve: Aida63 [Aida63] in /builds/workspace/Aida Pharo 1....etc... Receiver's instance variables: spec: a MetacelloMCVersionSpecLoader operator: nil loaderPolicy: a MetacelloLoaderPolicy disablePackageCache: false I could trigger this job if you want. -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-project] Jenkins: build scripts are now in public repository

by Igor Stasenko

On 12 July 2011 10:58, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Igor, > > please publish then server versions of build scripts like build13.sh, build.sh on git is based on build13.sh. The old build.sh was different in a way how it handles image stalls. There was loop waiting for output from image. And if nothing happens it kills VM process. Now since in 1.3 this is much less likely to happen (because it using non-interactive ui manager), we removed that. > build-kernel.sh etc. too. > it almost the same as build.sh.. but there are some difference. i started to examine it yesterday but then came home :) > -- Pavel > > On Mon, Jul 11, 2011 at 7:47 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 11 July 2011 19:33, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> What I great change. I think I have asked Marcus about them like 10 times :) >> >> So, i think you asked for a reason? :) >> Because now you have commit rights to this repository, nothing >> prevents you from doing what you wanted to do :) >> >> The changes are quite simple: >> Â - avoid using absolute paths (instead use $WORKSPACE) environment variable >> all scripts are starting from: >> >> if [ -z "$WORKSPACE" ] ; then >> Â Â Â Â WORKSPACE=`pwd` >> fi >> >> so, you can run them on your local machine, and they will work same on server. >> Of course if you don't make stupid mistakes... ( bah it's so easy to >> look like an idiot with these bash scripts. I have bash/sh !!!) >> >> When you need to invoke VM , use PHARO_VM environment variable. Which >> is set on slave to point to VM. >> Like: >> exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headless >> >> Of course, for testing freshly built VMs it may point to another >> place, but scripts will remain same. >> >> (tomorrow i will start migrating VM jobs from hudson to jenkins) >> Jenkins is more appeal and seems to be less buggy. :) >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-project] Socket objects created twice ?

by Henrik Sperre Johansen

Didn't really answer these, if it weren't obvious: On 12.07.2011 13:38, Sven Van Caekenberghe wrote: > Is there really only one OS level socket ? Yes, only the one returned from newXYZ gets registered externally. > Does this have to do with Sockets being in a WeakRegistry ? Yes, the other is used to release the externally registered resource when the one you created is no longer referenced (ie. to finalize it) Cheers, Henry

July 12, 2011

Re: [Pharo-project] Socket objects created twice ?

by Henrik Sperre Johansen

On 12.07.2011 13:38, Sven Van Caekenberghe wrote: > Hi All, > > I encountered something that I do not understand. I tried this in 1.2.2 and 1.4 with both my normal, older CogVM as well as the lastest one by Estaban. > > In a normal clean image, there would be not Socket instances. > > Socket allInstances size = 0 > > Now create any kind of Socket > > Socket new (or newTCP, newUDP) > > Now > > Socket allInstances size = 2 > > So Smalltalk reports two instances, but it seems they share the same socketHandle and semaphores, so one seems to be a shallow copy of the other. > > (Close the one instance, 3 timesRepeat: [ Smalltalk garbageCollect ] and they are both gone). > > Is this normal ? > Is there really only one OS level socket ? > Does this have to do with Sockets being in a WeakRegistry ? > > It is confusing to say the least. > > Sven Yes it's normal, one is the finalizer of the other. To differentiate them more easily, you could do Socket >> actAsFinalizer socketHandle := socketHandle bitInvert. and finalize self primSocketDestroyGently: socketHandle bitInvert. This will (99.9% likely at least) give a printstring of invalidSocketHandle for the finalizing Socket instance. Cheers, Henry

July 12, 2011

Re: [Pharo-project] Socket objects created twice ?

by Schwab,Wilhelm K

I have seen this too (1.1.1), and it bothered me. I *think* you will find that the handles of the two sockets are the same, but it "Just ain't right" (TM). Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sven Van Caekenberghe [sven(a)beta9.be] Sent: Tuesday, July 12, 2011 7:38 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] Socket objects created twice ? Hi All, I encountered something that I do not understand. I tried this in 1.2.2 and 1.4 with both my normal, older CogVM as well as the lastest one by Estaban. In a normal clean image, there would be not Socket instances. Socket allInstances size = 0 Now create any kind of Socket Socket new (or newTCP, newUDP) Now Socket allInstances size = 2 So Smalltalk reports two instances, but it seems they share the same socketHandle and semaphores, so one seems to be a shallow copy of the other. (Close the one instance, 3 timesRepeat: [ Smalltalk garbageCollect ] and they are both gone). Is this normal ? Is there really only one OS level socket ? Does this have to do with Sockets being in a WeakRegistry ? It is confusing to say the least. Sven

July 12, 2011