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

Re: [Pharo-project] loading OSProcess in Pharo1.3

by Johan Brichau

You are right... except that I am not using a ConfigurationOfOSProcess strange... my metacello config just points to the repository and loads the OSProcess package... why is it loading an older version? probably another config that I am loading that points to it? ... argh... thanks, at least I know now :-) On 10 Jul 2011, at 20:08, Mariano Martinez Peck wrote: > yes, it was. Probable nobody updated ConfigurationOfOSProcess as Johan is loading an old version. Try getting the last one or use #bleedingEdge > > On Sun, Jul 10, 2011 at 3:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > strnage I thought the new version of OS Process fixed that. > > On Jul 10, 2011, at 3:03 PM, Johan Brichau wrote: > > > Hi guys, > > > > I'm (finally) trying out the new Pharo1.3 > > Yesterday I had a couple of issues with build 13284 but 13285 seems to fix these. > > > > Great! > > > > But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to add its image startup script to the list right after ImageSegment's image startup script. > > However, it appears that #ImageSegment is no longer in the startup list, which yields an error. > > > > I don't know if this is expected, so I thought I should email it here. > > > > For now, I changed OSProcess so that it adds its startup script right after SmalltalkImage instead. > > I'm not sure if that is OK though... it's just a quick fix I made right now. I'm not sure what the prerequisites of OSProcess are in that respect. > > > > Any thoughts? > > > > Johan > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

July 10, 2011

Re: [Pharo-project] loading OSProcess in Pharo1.3

by Mariano Martinez Peck

yes, it was. Probable nobody updated ConfigurationOfOSProcess as Johan is loading an old version. Try getting the last one or use #bleedingEdge On Sun, Jul 10, 2011 at 3:16 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > strnage I thought the new version of OS Process fixed that. > > On Jul 10, 2011, at 3:03 PM, Johan Brichau wrote: > > > Hi guys, > > > > I'm (finally) trying out the new Pharo1.3 > > Yesterday I had a couple of issues with build 13284 but 13285 seems to > fix these. > > > > Great! > > > > But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to > add its image startup script to the list right after ImageSegment's image > startup script. > > However, it appears that #ImageSegment is no longer in the startup list, > which yields an error. > > > > I don't know if this is expected, so I thought I should email it here. > > > > For now, I changed OSProcess so that it adds its startup script right > after SmalltalkImage instead. > > I'm not sure if that is OK though... it's just a quick fix I made right > now. I'm not sure what the prerequisites of OSProcess are in that respect. > > > > Any thoughts? > > > > Johan > > > -- Mariano http://marianopeck.wordpress.com

July 10, 2011

Re: [Pharo-project] webdoc

by Camillo Bruni

Thanks for the response :) On 2011-07-09, at 13:59, Tudor Girba wrote: > Great job. It looks nice indeed: > - I like the expanding of methods > - I like the section expanders (from Instance / Class Methods Summary) > - The search in the frames from the left is quite snappy > - The subclassing showing / hiding > - The inheritance diagram > - I like the full urls like: > http://rmod.lille.inria.fr/webdoc/doc/class/BlockCannotReturn > - The look is clean > > > While playing with it, I also found a couple of issues: > - sometimes it freezes in the sense that I select a class and nothing happens on the right frame. - indeed this is annoying, this should be solved once the hole image is rendered statically > - I like the full urls, but, the problem is that they are hidden in the frame, so it's difficult to spot them - right, that I solved at some point as well, but I must have broken it again. there was some JS running which create bookmarkable URLs in the main-page > - Some links in the Overview section are broken. It looks like there is some sort of pattern matching and there are false positives. For example, on the above mentioned page, there are links to "as:" and "ensure:" - yeah I guess I can disable the parsing for selectors :) > - The preview that pops out when hovering over methods is too slow and it only shows a white box for a long time. I would disable it for now - indeed annoying, again this is solved once the content is served statically > - The inheritance diagram is interesting, but I do not exactly understand what it shows. For example, I selected Error and the diagram is like the one in the attachment. It looks like the current class, is displayed with more methods, but I do not understand how the rest of the classes were selected. - as a lame excuse ;) I simply took over existing code, will investigate that, since its rather bizarr > Cheers, > Doru > > On 9 Jul 2011, at 13:30, Noury Bouraqadi wrote: >> very cool >> On 8 juil. 2011, at 21:29, Camillo Bruni wrote: >>> hi all, >>> >>> damien and me finally found enough time at the pharo sprint to put a working version of webdoc online: >>> >>> http://rmod.lille.inria.fr/webdoc/ >>> >>> Please test and give some feedback :) (the major issue right now is speed, but since we plan on using it only as an html generator which later-on should be served statically this shouldn't be much of a problem) >>> >>> cami

July 10, 2011

Re: [Pharo-project] webdoc

by Camillo Bruni

On 2011-07-09, at 15:37, Sven Van Caekenberghe wrote: > On 08 Jul 2011, at 21:29, Camillo Bruni wrote: > >> damien and me finally found enough time at the pharo sprint to put a working version of webdoc online: >> >> http://rmod.lille.inria.fr/webdoc/ > > Yes this is very cool! > > Is it easy to install this in one's own image ? It's more or less easy :) but I haven't created a Configuration yet... meaning that you have to fetch a couple of things - Seaside - Seaside - REST (+ the pharo stuff) - PPMarkdownParser - PetitParser - RPackage - SimpleWebdoc - WebDoc I think thats it :). I think I will create a configuration tomorrow, so its easier to distribute, camillo

July 10, 2011

Re: [Pharo-project] Troubles with #flushCache and #run:with:in:

by Lukas Renggli

Created http://code.google.com/p/pharo/issues/detail?id=4512. On 10 July 2011 15:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > no we care but have no idea/too busy > Can you add a bug entry so that we do not forget it. > Tx > > > On Jul 10, 2011, at 1:30 PM, Lukas Renggli wrote: > >> Ping! >> >> Does nobody care about method coverage? If so, we should remove it >> from the image. >> >> Is it just broken for me? >> >> Lukas >> >> >> On 1 July 2011 09:32, Lukas Renggli <renggli(a)gmail.com> wrote: >>> Hi Eliot, >>> >>> I am using one of the latest VMs from your site (VM.r2434) and I >>> continue to have subtle problems with objects as methods (#flushCache, >>> #run:with:in:). >>> >>> The issue is that the test coverage in Pharo is kind of broken on Cog >>> for a long time already. It reports methods as not covered that are >>> clearly covered, and tests seem to randomly fail. >>> >>> I suspected that there is something wrong with the coverage code >>> itself. So I started to experiment with TestCoverage>>flushCache and >>> noticed that the current implementation >>> >>> Â Â TestCoverage>>flushCache >>> Â Â Â Â self reference methodSymbol flushCache >>> >>> performs not that well: The set of not covered methods is wrong and >>> many tests suddenly fail. If I replace it with >>> >>> Â Â TestCoverage>>flushCache >>> Â Â Â Â self reference actualClass flushCache >>> >>> I actually get accurate coverage information, but there are still a >>> few tests constantly failing. I tried to use all possible combinations >>> of #flushCache (also calling it on the compiled method), but only >>> flushing the cache on the class seems to work properly. So far so >>> good, but I really wonder what the correct way is to flush the cache? >>> :-) >>> >>> For my experiments I was using the package 'AST-Tests-Semantics'. This >>> is a small package with lots of test methods that cover each method >>> but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real" >>> problem is that when running these tests in coverage mode, the same 4 >>> tests always fail: >>> >>> Â Â RBSemanticTest>>testBlockScope >>> Â Â RBSemanticTest>>testCascadeReceiver >>> Â Â RBSemanticTest>>testClassVariableBinding >>> Â Â RBSemanticTest>>testGlobalVariableBinding >>> >>> Not sure of how to debug that? Do you have an idea why these otherwise >>> passing tests suddenly fail? If you want to try to reproduce you can >>> use any Pharo image with the tests loaded, or use those that I used: >>> >>> Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >>> Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >>> >>> Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'. >>> >>> Any help or clarification would be appreciated :-) >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > -- Lukas Renggli www.lukas-renggli.ch

July 10, 2011

Re: [Pharo-project] Troubles with #flushCache and #run:with:in:

by StÃ©phane Ducasse

no we care but have no idea/too busy Can you add a bug entry so that we do not forget it. Tx On Jul 10, 2011, at 1:30 PM, Lukas Renggli wrote: > Ping! > > Does nobody care about method coverage? If so, we should remove it > from the image. > > Is it just broken for me? > > Lukas > > > On 1 July 2011 09:32, Lukas Renggli <renggli(a)gmail.com> wrote: >> Hi Eliot, >> >> I am using one of the latest VMs from your site (VM.r2434) and I >> continue to have subtle problems with objects as methods (#flushCache, >> #run:with:in:). >> >> The issue is that the test coverage in Pharo is kind of broken on Cog >> for a long time already. It reports methods as not covered that are >> clearly covered, and tests seem to randomly fail. >> >> I suspected that there is something wrong with the coverage code >> itself. So I started to experiment with TestCoverage>>flushCache and >> noticed that the current implementation >> >> TestCoverage>>flushCache >> self reference methodSymbol flushCache >> >> performs not that well: The set of not covered methods is wrong and >> many tests suddenly fail. If I replace it with >> >> TestCoverage>>flushCache >> self reference actualClass flushCache >> >> I actually get accurate coverage information, but there are still a >> few tests constantly failing. I tried to use all possible combinations >> of #flushCache (also calling it on the compiled method), but only >> flushing the cache on the class seems to work properly. So far so >> good, but I really wonder what the correct way is to flush the cache? >> :-) >> >> For my experiments I was using the package 'AST-Tests-Semantics'. This >> is a small package with lots of test methods that cover each method >> but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real" >> problem is that when running these tests in coverage mode, the same 4 >> tests always fail: >> >> RBSemanticTest>>testBlockScope >> RBSemanticTest>>testCascadeReceiver >> RBSemanticTest>>testClassVariableBinding >> RBSemanticTest>>testGlobalVariableBinding >> >> Not sure of how to debug that? Do you have an idea why these otherwise >> passing tests suddenly fail? If you want to try to reproduce you can >> use any Pharo image with the tests loaded, or use those that I used: >> >> http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >> http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… >> >> Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'. >> >> Any help or clarification would be appreciated :-) >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

July 10, 2011

Re: [Pharo-project] loading OSProcess in Pharo1.3

by StÃ©phane Ducasse

strnage I thought the new version of OS Process fixed that. On Jul 10, 2011, at 3:03 PM, Johan Brichau wrote: > Hi guys, > > I'm (finally) trying out the new Pharo1.3 > Yesterday I had a couple of issues with build 13284 but 13285 seems to fix these. > > Great! > > But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to add its image startup script to the list right after ImageSegment's image startup script. > However, it appears that #ImageSegment is no longer in the startup list, which yields an error. > > I don't know if this is expected, so I thought I should email it here. > > For now, I changed OSProcess so that it adds its startup script right after SmalltalkImage instead. > I'm not sure if that is OK though... it's just a quick fix I made right now. I'm not sure what the prerequisites of OSProcess are in that respect. > > Any thoughts? > > Johan

July 10, 2011

[Pharo-project] loading OSProcess in Pharo1.3

by Johan Brichau

Hi guys, I'm (finally) trying out the new Pharo1.3 Yesterday I had a couple of issues with build 13284 but 13285 seems to fix these. Great! But I'm now trying to load OSProcess in Pharo 1.3 and OSProcess tries to add its image startup script to the list right after ImageSegment's image startup script. However, it appears that #ImageSegment is no longer in the startup list, which yields an error. I don't know if this is expected, so I thought I should email it here. For now, I changed OSProcess so that it adds its startup script right after SmalltalkImage instead. I'm not sure if that is OK though... it's just a quick fix I made right now. I'm not sure what the prerequisites of OSProcess are in that respect. Any thoughts? Johan

July 10, 2011

Re: [Pharo-project] Troubles with #flushCache and #run:with:in:

by Lukas Renggli

Ping! Does nobody care about method coverage? If so, we should remove it from the image. Is it just broken for me? Lukas On 1 July 2011 09:32, Lukas Renggli <renggli(a)gmail.com> wrote: > Hi Eliot, > > I am using one of the latest VMs from your site (VM.r2434) and I > continue to have subtle problems with objects as methods (#flushCache, > #run:with:in:). > > The issue is that the test coverage in Pharo is kind of broken on Cog > for a long time already. It reports methods as not covered that are > clearly covered, and tests seem to randomly fail. > > I suspected that there is something wrong with the coverage code > itself. So I started to experiment with TestCoverage>>flushCache and > noticed that the current implementation > > Â Â TestCoverage>>flushCache > Â Â Â Â self reference methodSymbol flushCache > > performs not that well: The set of not covered methods is wrong and > many tests suddenly fail. If I replace it with > > Â Â TestCoverage>>flushCache > Â Â Â Â self reference actualClass flushCache > > I actually get accurate coverage information, but there are still a > few tests constantly failing. I tried to use all possible combinations > of #flushCache (also calling it on the compiled method), but only > flushing the cache on the class seems to work properly. So far so > good, but I really wonder what the correct way is to flush the cache? > :-) > > For my experiments I was using the package 'AST-Tests-Semantics'. This > is a small package with lots of test methods that cover each method > but one (RBSemanticAnnotationMisssing>>#isResumable). Now the "real" > problem is that when running these tests in coverage mode, the same 4 > tests always fail: > > Â Â RBSemanticTest>>testBlockScope > Â Â RBSemanticTest>>testCascadeReceiver > Â Â RBSemanticTest>>testClassVariableBinding > Â Â RBSemanticTest>>testGlobalVariableBinding > > Not sure of how to debug that? Do you have an idea why these otherwise > passing tests suddenly fail? If you want to try to reproduce you can > use any Pharo image with the tests loaded, or use those that I used: > > Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… > Â Â http://jenkins.lukas-renggli.ch/job/Development/lastSuccessfulBuild/artifac… > > Open the Test Runner, select 'AST-Tests-Semantics' and 'Run Coverage'. > > Any help or clarification would be appreciated :-) > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

July 10, 2011

[Pharo-project] [update 1.3] #13285

by StÃ©phane Ducasse

13285 ----- ThreadSafeTranscript install

July 9, 2011