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

Re: [Pharo-dev] [regression reporter]regression occurred

by Camillo Bruni

I think we already checked that, but it has nothing to do the with a particular windows slave, no? On 2013-09-05, at 10:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > On 05 Sep 2013, at 11:25, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> On Thu, Sep 5, 2013 at 9:51 AM, <no-reply(a)ci.inria.fr> wrote: >>> 1 regressions found. >>> Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion >> >> >> it seems that this test fails very often. Can we do anything about it? > > It only fails on Windows, and only from time to time ;-) > > All it does is basically access one HTTPS URL > > https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xpath=/… > > testGetPharoVersion > | client lastBuildVersion version | > self ensureSocketStreamFactory. > self isNativeSSLPluginPresent ifFalse: [ ^ self ]. > lastBuildVersion := (client := ZnClient new) > beOneShot; > get: 'https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xpath=/…'. > self assert: client isSuccess. > self assert: (client response contentType matches: ZnMimeType applicationXml). > self assert: client response contentLength > 0. > self assert: lastBuildVersion notNil. > self assert: lastBuildVersion isString. > self assert: lastBuildVersion size > 0. > version := (lastBuildVersion copyAfter: $>) copyUpTo: $<. > self deny: version isEmpty > > This is a regression test for a bug that once existed, long ago. Normally, I try to add such a test for each issue that I fix. > > Sven > >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > >

Sept. 5, 2013

[update 3.0] #30370

by Marcus Denker

30370 ----- 11529 MetacelloConfigurationBrowser open not working https://pharo.fogbugz.com/f/cases/11529 11062 Remove old compiler API from Pharo image Part 2 https://pharo.fogbugz.com/f/cases/11062 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1239.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Tests-MarcusDenk… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusRefactoring-MarcusDen… http://smalltalkhub.com/mc/Pharo/Pharo30/main/NativeBoost-Core-MarcusDenker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1594.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.522.diff

Sept. 5, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Sven Van Caekenberghe

On 05 Sep 2013, at 11:25, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Thu, Sep 5, 2013 at 9:51 AM, <no-reply(a)ci.inria.fr> wrote: >> 1 regressions found. >> Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion > > > it seems that this test fails very often. Can we do anything about it? It only fails on Windows, and only from time to time ;-) All it does is basically access one HTTPS URL https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xpath=/… testGetPharoVersion | client lastBuildVersion version | self ensureSocketStreamFactory. self isNativeSSLPluginPresent ifFalse: [ ^ self ]. lastBuildVersion := (client := ZnClient new) beOneShot; get: 'https://ci.inria.fr/pharo/job/Pharo-2.0/lastSuccessfulBuild/api/xml?xpath=/…'. self assert: client isSuccess. self assert: (client response contentType matches: ZnMimeType applicationXml). self assert: client response contentLength > 0. self assert: lastBuildVersion notNil. self assert: lastBuildVersion isString. self assert: lastBuildVersion size > 0. version := (lastBuildVersion copyAfter: $>) copyUpTo: $<. self deny: version isEmpty This is a regression test for a bug that once existed, long ago. Normally, I try to add such a test for each issue that I fix. Sven > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Sept. 5, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by David T. Lewis

On Thu, Sep 05, 2013 at 11:18:27AM +0200, Goubier Thierry wrote: > Thanks. > > I have merged -dtl.33 and two more change in > OSProcess-Base-ThierryGoubier.35 on > http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main/ (osVersion and > vmVersion), if you want to merge them as well. > Thanks! > I have a question: are you sure about the perform: #delete in OSProcess > class>>#deleteFileNamed: ? ensureDelete/ensureDeleted have a different > behavior than #delete. > No, I am not sure about this. It is probably a bug. If you have a correction, I appreciate it. Thanks a lot for your help :) Dave

Sept. 5, 2013

Re: [Pharo-dev] How to contribute updates

by Camillo Bruni

I changed some settings in FogBugz, can you try to edit the wiki again? https://pharo.fogbugz.com/default.asp?pg=pgWiki&ixWikiPage=39&command=edit ... and yes, these pages outdate quicker than I thought :( On 2013-09-05, at 06:38, Stephan Eggermont <stephan(a)stack.nl> wrote: > Found some improvements for the wiki page on fogbugz. > I don't see a way to make changes myself. > - refer to the smalltalkhub repositories, explain the squeaksource > history; > - the flow is not so clear in the difference between describing the > contribution and where to put it (attachment, paste log message?) > - no procedure for merging described > - 'you are ready for the next step' which is? > - unstable refers to Pharo20 instead of 30 > - how to handle fixes for both 20 and 30 > > Stephan >

Sept. 5, 2013

[update 3.0] #30369

by Marcus Denker

Sept. 5, 2013

How to contribute updates

by Stephan Eggermont

Found some improvements for the wiki page on fogbugz. I don't see a way to make changes myself. - refer to the smalltalkhub repositories, explain the squeaksource history; - the flow is not so clear in the difference between describing the contribution and where to put it (attachment, paste log message?) - no procedure for merging described - 'you are ready for the next step' which is? - unstable refers to Pharo20 instead of 30 - how to handle fixes for both 20 and 30 Stephan

Sept. 5, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Damien Cassou

On Thu, Sep 5, 2013 at 9:51 AM, <no-reply(a)ci.inria.fr> wrote: > 1 regressions found. > Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion it seems that this test fails very often. Can we do anything about it? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 5, 2013

Re: [Pharo-dev] OSProcess for Pharo3.0

by Goubier Thierry

Thanks. I have merged -dtl.33 and two more change in OSProcess-Base-ThierryGoubier.35 on http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main/ (osVersion and vmVersion), if you want to merge them as well. I have a question: are you sure about the perform: #delete in OSProcess class>>#deleteFileNamed: ? ensureDelete/ensureDeleted have a different behavior than #delete. Regards, Thierry Le 05/09/2013 04:21, David T. Lewis a Ã©crit : > On Wed, Sep 04, 2013 at 02:17:29PM +0200, Marcus Denker wrote: >> >> On Sep 4, 2013, at 2:13 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: >> >>> On Tue, Sep 03, 2013 at 10:51:33PM -0400, David T. Lewis wrote: >>>> On Tue, Sep 03, 2013 at 01:48:46PM +0200, Goubier Thierry wrote: >>>>> >>>>> Le 03/09/2013 13:36, David T. Lewis a ?crit : >>>>>> >>>>>> Can you post the method here first? I'd like to check it on some Squeak >>>>>> images >>>>>> before it goes into the repository. >>>>> >>>>> Here it is (at least an example): >>>>> >>>>> in OSProcess class >>>>> >>>>> isPharo3AndLater >>>>> "Test if we are on Pharo 3.0" >>>>> >>>>> ^ (Smalltalk classNamed: 'SystemVersion') >>>>> ifNil: [ false ] >>>>> ifNotNil: [ :v | v current type = 'Pharo' and: [ v current >>>>> major >= 3 ] ] >>>> >>>> The idea is right, but the details can be a PITA ;-) >>>> >>>> - In Squeak trunk, class SystemVersion exists. But it does not understand #type, so this fails at runtime. >>>> >>>> - There are no implementors of #major in Squeak (but this can be rewritten using #perform:). >>>> >>>> - In Squeak 3.8, #ifNil:ifNotNil: requires a block with no arguments. >>>> >>>> I did not check the other Pharo versions. >>>> >>>> Something like this might work: >>>> >>>> isPharo3AndLater >>>> Smalltalk >>>> at: #SystemVersion >>>> ifPresent: [:cls | ((cls canUnderstand: #type) and: [ cls canUnderstand: #major ]) >>>> ifTrue: [^ cls current type = 'Pharo' and: [ cls current major >= 3 ]]]. >>>> ^false >>>> >>> >>> >>> I am also checking the platform subtype implementation (OSProcess platformSubtype). >>> >>> In Pharo: >>> >>> Smalltalk os subtype ==> 'i686' >>> >>> This reflects the processor type, not the os subtype (it should be 'x86_64' on my PC). >>> >>> Is this intentional? >>> >> I don't think so. >> >> Marcus >> > > Thanks Goubier and Marcus, > > I made the updates to OSProcess and CommandShell to handle system version and subtype > in Pharo 3.0. > > I did not yet update ConfigurationOfOSProcess or ConfigurationOfCommandShell, but the > latest versions for Squeak/Pharo are in OSProcess-dtl.83 and CommandShell-dtl.73 in > the SqueakSource repositories. > > Dave > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Sept. 5, 2013

Re: [Pharo-dev] [About Documentation] Teach, Don't Tell / Steve Losh

by kilon

A big thank you from me as well , PBE definetly made possible to use Pharo. If I had to read pharo code to understand how to work I would be right back with python by now. Pharo can learn tons of things from the success of python , I am very glad to see that you guys put big priority on Documentation as python does. Youtube also has loads of squeak and pharo video tutorials. So thing actually are much better than I initially feared. The problems is that smaltlalkers tend to overestimate smalltalk and not document their code. They believe too much into "self documented" nonesense and this article hits the nail on the head concerning this problem. AFAIK the best way to code is by writting documentation at the same time. Unless you are the type of coder that tends to rewrite his library 10 times before releasing, which I seriously doubt. Python has been a huge success as a language because developer take documentation extremely seriously. I have not forget about documenting nativeboost, I will try to write a small article on my blog about nativeboost and the things I learned which may help you use it as part of the nativeboost documentation. If you have any request dont forget to ping me. -- View this message in context: http://forum.world.st/About-Documentation-Teach-Don-t-Tell-Steve-Losh-tp470… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 5, 2013