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

Re: [Pharo-project] Fileout the test results

by Simon Denier

On 24 sept. 09, at 15:34, Mariano Martinez Peck wrote: > > > 2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > > On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: > >> Hi folks: Several times, I wanted to send by email for example, the >> results of running some tests. The only and ugly way I found to do >> this is using PrintScreen and send the screenshots. Now, the >> question is, is there a way to file out the results? Not only the >> amount (the number) of success, failures, error, expected failures, >> but also which tests where the failures, errors, etc. > > You can take a look at http://www.squeaksource.com/TestServerSimple.html > for some samples of code. > > > Wow! I wasn't aware of that project. What's the idea of that > project? I didn't find any information there. Just having a simple automated engine to run tests for Moose automatically. The code is adapted from some previous project in Switzerland and, to be honest, it's pretty much a hack leaving plenty of dead code behind. Configuration of projects to test is hard-coded. I am working on a new TestServer which would use Metacello configurations. > > However, I was thinking in something much more simpler. For newbies > (like me hahaha) or people who may want to contribute to Pharo just > testing and sending the reports. Perhaps a simple button in Test > Runner that says "Fileout results". So that he can send the file to > the mailing list or whatever. > > what do you think ? That's a very good idea. We need more power tools for the tests anyway. I would also like to see more powerful features for regression testing (there is a basic test history only accessible through the TestRunner right now) > >> >> I would love to do this from the Test Runner, no by code. >> >> Best, >> >> Mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > 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 -- Simon

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Mariano Martinez Peck

2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > > On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: > > Hi folks: Several times, I wanted to send by email for example, the results > of running some tests. The only and ugly way I found to do this is using > PrintScreen and send the screenshots. Now, the question is, is there a way > to file out the results? Not only the amount (the number) of success, > failures, error, expected failures, but also which tests where the failures, > errors, etc. > > > You can take a look at http://www.squeaksource.com/TestServerSimple.html for > some samples of code. > > Wow! I wasn't aware of that project. What's the idea of that project? I didn't find any information there. However, I was thinking in something much more simpler. For newbies (like me hahaha) or people who may want to contribute to Pharo just testing and sending the reports. Perhaps a simple button in Test Runner that says "Fileout results". So that he can send the file to the mailing list or whatever. what do you think ? > > I would love to do this from the Test Runner, no by code. > > Best, > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Simon Denier

On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: > Hi folks: Several times, I wanted to send by email for example, the > results of running some tests. The only and ugly way I found to do > this is using PrintScreen and send the screenshots. Now, the > question is, is there a way to file out the results? Not only the > amount (the number) of success, failures, error, expected failures, > but also which tests where the failures, errors, etc. You can take a look at http://www.squeaksource.com/ TestServerSimple.html for some samples of code. > > I would love to do this from the Test Runner, no by code. > > Best, > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

Sept. 24, 2009

[Pharo-project] Fileout the test results

by Mariano Martinez Peck

Hi folks: Several times, I wanted to send by email for example, the results of running some tests. The only and ugly way I found to do this is using PrintScreen and send the screenshots. Now, the question is, is there a way to file out the results? Not only the amount (the number) of success, failures, error, expected failures, but also which tests where the failures, errors, etc. I would love to do this from the Test Runner, no by code. Best, Mariano

Sept. 24, 2009

Re: [Pharo-project] '.2e2' asNumber ?

by Schwab,Wilhelm K

Nicolas, Silent failures are **BAD**. I always like to compare things to #at: and #at:ifAbsent:. #at: will answer the indicated item or raise an exception. #at:ifAbsent: allows one to customize the behavior and w/o the expense of setting up an exception handler, which is great if the error (bounds in this case) can be understood and corrected locally. Of course, structured exceptions arose to handle the common situation in which I find an error but only you can tell what to do about it, and we are working on completely different parts of the system. This whole debate arises again with end-of-stream exceptions: http://code.google.com/p/pharo/wiki/StreamsForRobustSoftware I am using the additional protocol approach with good results, but should try to make some time to test your pluggable exception idea. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Nicolas Cellier Sent: Thursday, September 24, 2009 3:19 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] '.2e2' asNumber ? The two problems were identified from the beginning: 1) 2.e5 and .2 did work in old squeak images, but no more with SqNumberParser Rationale: SqNumberParser is for parsing number literals in squeak syntax, and those extensions are not identified squeak syntax If you need these syntax, the best thing is to subclass the NumberParser. For example, I must have a FORTRANNumberParser available somewhere... 2) Silently returning zero in case of error. This was one of the goal of SqNumberParser: let programmer choose the appropriate behaviour - raise an Exception - answer nil - answer a default value (zero) The last solution has been connected to Number class>>#readFrom: for historical compatibility reasons. I agree this conservative choice was unfortunate. Pharo should not fear and break compatibility on such dumb behaviours. Nicolas 2009/9/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I imagine that nicolas will let us know. > If you have tests we would love to integrate them so that we can > detect that. > > Stef > > On Sep 23, 2009, at 11:25 PM, John M McIntosh wrote: > >> I noticed that in Squeak and earlier version of Pharo doing '.2e2' >> asNumber would return 20.0 or '.2' asNumber would return 0.2 >> >> but currently in Pharo those return 0, without error, comment, or >> other hand waving. >> Good thing I have Sunits... >> >> So is this a bug or feature? >> >> Hint obviously in the Fractions calculator people are lazy and enter . >> 2e2 or .2 without the leading zero... >> >> -- >> = >> = >> = >> = >> = >> ===================================================================== >> = John M. McIntosh <johnmci(a)smalltalkconsulting.com> Â Twitter: >> squeaker68882 >> Corporate Smalltalk Consulting Ltd. Â http:// >> www.smalltalkconsulting.com = = = = = >> ===================================================================== >> = >> >> >> >> >> >> _______________________________________________ >> 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

Sept. 24, 2009

Re: [Pharo-project] '.2e2' asNumber ?

by Nicolas Cellier

The two problems were identified from the beginning: 1) 2.e5 and .2 did work in old squeak images, but no more with SqNumberParser Rationale: SqNumberParser is for parsing number literals in squeak syntax, and those extensions are not identified squeak syntax If you need these syntax, the best thing is to subclass the NumberParser. For example, I must have a FORTRANNumberParser available somewhere... 2) Silently returning zero in case of error. This was one of the goal of SqNumberParser: let programmer choose the appropriate behaviour - raise an Exception - answer nil - answer a default value (zero) The last solution has been connected to Number class>>#readFrom: for historical compatibility reasons. I agree this conservative choice was unfortunate. Pharo should not fear and break compatibility on such dumb behaviours. Nicolas 2009/9/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I imagine that nicolas will let us know. > If you have tests we would love to integrate them so that we can > detect that. > > Stef > > On Sep 23, 2009, at 11:25 PM, John M McIntosh wrote: > >> I noticed that in Squeak and earlier version of Pharo doing >> '.2e2' asNumber >> would return 20.0 >> or '.2' asNumber >> would return 0.2 >> >> but currently in Pharo those return 0, without error, comment, or >> other hand waving. >> Good thing I have Sunits... >> >> So is this a bug or feature? >> >> Hint obviously in the Fractions calculator people are lazy and enter . >> 2e2 or .2 without the leading zero... >> >> -- >> = >> = >> = >> = >> = >> ====================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Â Twitter: >> squeaker68882 >> Corporate Smalltalk Consulting Ltd. Â http:// >> www.smalltalkconsulting.com >> = >> = >> = >> = >> = >> ====================================================================== >> >> >> >> >> >> _______________________________________________ >> 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 >

Sept. 24, 2009

Re: [Pharo-project] Closure fixes

by StÃ©phane Ducasse

Mike this is really cool. Thanks a ***lot*** I got 7281 run, 7182 passes, 2 expected failures, 80 failures, 15 errors, 2 unexpected passes while reading the code and checking differences. I noticed that the CompiledMethod>>compilerClass, parserClass and decompilerClass got changed and hardcoded the Compiler instead of using compilerClass and others. http://code.google.com/p/pharo/issues/detail?id=1238 Now for the integration On Sep 24, 2009, at 12:23 AM, Michael Roberts wrote: > "A. Load Gofer" > ScriptLoader new installGofer. > > "B. Install packages" > | gofer packages | > gofer := Gofer new. > gofer url: 'http://www.squeaksource.com/PharoTaskForces'. > > packages := #( > "Part 2.1" > 'Kernel-MikeRoberts.408' > > "Part 3" > 'CompilerTests-MikeRoberts.21' > 'KernelTests-MikeRoberts.150' > 'Compiler-MikeRoberts.130' > > "Part 4" > 'Compiler-MikeRoberts.131' > > "Part 5" > 'Kernel-MikeRoberts.409' > > "Part 6" > 'Kernel-MikeRoberts.411' > > "Part 7" > 'System-Changes-MikeRoberts.13' > 'System-Download-MikeRoberts.11' > 'System-Support-MikeRoberts.89' > > "Part 8" > 'Tools-MikeRoberts.202' > > "Part 9 - setup recompile" > 'System-Support-MikeRoberts.90'). > > packages do: [:each | > gofer copy > add: each; > load]. > > "C. Recompile" > Utilities initializeClosures. > Utilities compileUsingClosures. > > "D. Run the tests please" > TestRunner open > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 24, 2009

Re: [Pharo-project] '.2e2' asNumber ?

by StÃ©phane Ducasse

I imagine that nicolas will let us know. If you have tests we would love to integrate them so that we can detect that. Stef On Sep 23, 2009, at 11:25 PM, John M McIntosh wrote: > I noticed that in Squeak and earlier version of Pharo doing > '.2e2' asNumber > would return 20.0 > or '.2' asNumber > would return 0.2 > > but currently in Pharo those return 0, without error, comment, or > other hand waving. > Good thing I have Sunits... > > So is this a bug or feature? > > Hint obviously in the Fractions calculator people are lazy and enter . > 2e2 or .2 without the leading zero... > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 24, 2009

[Pharo-project] Fwd: could you have a look athe HostSystemMenusTest

by StÃ©phane Ducasse

Does anybody know because I simply forgot. Stef Begin forwarded message: > From: John M McIntosh <johnmci(a)smalltalkconsulting.com> > Date: September 23, 2009 11:42:55 PM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: could you have a look athe HostSystemMenusTest > Reply-To: johnmci(a)smalltalkconsulting.com > > Ok, you removed the 'File' menu on purpose then? That use to contain > the 'Quit do not save' menu item > If so the tests fail because I assume that menu is there. So I can > fix it, if your intent was to remove the File menu > > > On 2009-09-23, at 2:07 PM, StÃ©phane Ducasse wrote: > >> >> http://gforge.inria.fr/frs/download.php/23266/PharoCore-1.0-10451-BETA.zip >> Stef >> >> >> >> On Sep 23, 2009, at 11:01 PM, John M McIntosh wrote: >> >>> Sure, you have a pointer to an image? >>> >>> On 2009-09-23, at 1:48 PM, StÃ©phane Ducasse wrote: >>> >>>> Hi john >>>> >>>> I'm trying to fix some of the pending tests in pharo that are >>>> yellow but I do not know what to do >>>> to fix the HostSystemMenusTest. >>>> >>>> Could you have a look? >>>> >>>> Stef >>> >>> -- >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> ==================================================================== >>> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: >>> squeaker68882 >>> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> ==================================================================== >>> >>> >>> >>> >> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > >

Sept. 24, 2009

Re: [Pharo-project] Deploying Seaside: A tutorial

by Schwab,Wilhelm K

Miguel, I maintain it is not as trivial as some in the Seaside world keep suggesting, and sice I'm not alone in finding new ways that things fail to "just work," I stand by it. You appear to have completely missed my comments on ipv4/6. There are defects in Pharo's NetNameResolver, and they need to be fixed. It has nothing to do with Seaside, other than the defects prevent some of the finer points of customizing the certificate and possibly (depending on what is actually required) hints for apache configuration. I look forward to your blog. Hopefully it can be as simple as you suggest. Part of my interest in things like Apacheat is to capture the details to remove (to the extent possible) any human error components. BTW, it is not *me* who is afraid of Linux. I agree that Windows is much more to be feared. There are still a few things that keep me tied to it, and my interest in Pharo is to cut the few remaining chains. One of them will require a LOT of sawing, I'm afraid. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Miguel Enrique CobÃ¡ Martinez Sent: Wednesday, September 23, 2009 11:29 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Deploying Seaside: A tutorial El miÃ©, 23-09-2009 a las 10:43 -0400, Schwab,Wilhelm K escribiÃ³: > Sef, Miguel, > > I am very pleased to see you tackling this problem. Answers I > received from elsewhere "oh, that's trivial..." were not at all > helpful. Some web sites were helpful, but it was not always clear > whether or not they were complete solutions. One comment (there might > be more by now??) to the new book mentions complexity with newer Linux > distributions or something. I should review that, but I'm on a roll > :) > What type of complexity. My setup just use a bare bones OS install with the security configs applied and then just Squeak VM, Seaside and Magma. Nothing else. > I think we should build some tools to capture the details, and I have been working toward that. The problem is complicated slightly by conflicting writings, and perhaps that the target moves over time. Another wrinkle for me is that I want https connections. > My production server use https for all the site. It is going to be the last post, after the load testing one. Modify the lighttpd.conf config to add https to the mix. By the way this is a responsibility for the webwerver/proxy not for seaside. Don't do it on Seaside. The requests arrive encrypted to the webserver and then the webserver pass them unencrypted to the Seaside images that are behind. In fact the Seaside code doesn't know anything about ssl, just it asks Seaside to add the #https protocol in all the urls that it generates. But that is a one-liner in the initializacion code of the application. Give me a couple more of days and I will explain it on the blog. > Things I can offer, in varying stages of dis-repair: > > (1) OpenSSLCertificateFactory. I started this under Dolphin and was still thinking in Windows terms; I now consider Windows to be analogous to a draining wound in a part of my body I hope to keep. I still do some Windows-specific things, but the factory itself is designed to run on Linux; it would probably also be workable on a Mac, given its unix roots. > > I found openssl.exe to be slightly uncooperative. It would have been nice to have a library with entry points or at worst an executable willing to take arguments on the command line. All I could think to do was to create a configuration file with easily-recognized tags (e.g. COMMON_NAME) and to write a customized version of the file into a specified location with values provided as arguments to the method that does the work. I know I ran this on Linux at least once, but now I can't find all of the code (yet). It looks like it was one of my earlier efforts with SIF, which does not do a very good job with Dolphin's virtual categories, turning them into things that severely confuse Monticello, effectively unpackaging methods. > > The factory is really only of value to those wanting to self-sign a certificate. Some object mightily to this concept, but it works and it's FREE. I have no plans to make this work on Windows, because Linux shell scripting is remakably more rational than are Windows(TM) batch files. > > > (2) Apacheat. > > (2a) This is something that I see as needing to work on Windows, since I do not (yet) expose Linux servers to the world. However, I have also reduced it to creating a batch file and a .reg file to configure a service (interestingly, that has broken AGAIN, this time on win2k3). It uses srvany (or whatever the correct name is) to run the vm as a service. Have I mentioned that I am tiring of Windows? > I understand the part of tiring of windows. I don't understand why you have fear of exposing Linux to the internet and not Windows. I have the exact opposite fears ;) > (2b) It also has some code that iterates the Seaside apps and writes virtual host entries suitable for copying into an apache configuration file. The method in the new book might be simple enough to not bother with anything beyond a reference to where to find the relevant setup. > > > Parts of the above depend on being able to get a fully qualified name for the local machine, and NetNameResolver is more than slightly broken in that area. I am convinced that it invokes primitives that are known to fail for IPv4 on IPv4 networks. I have something that appears to work on both systems on xp (perhaps IPv6) and 2k3 (IPv4). I need to try it again on Linux, and might soon have the ability to try Linux on another network - in fact my new discontinued $399.99 laptop is being delivered today. Tux and I are very excited. Having recently tried Vista for a few days, I plan to try to begin repartitioning this drive before Vista can so much as boot ;) Ok, maybe I should let it boot just to see if everything works; I'll think about it. > Don't even follow that path. The seaside application don't ever be exposed to the world. Just the webserver doing proxy to them. So is the webserver that must know about fqdn and ssl and virtualhosting and other websites on the same install, etc. Seaside just do what it does better, run "applications". > Back to work. > > Bill Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 24, 2009