March 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14382

by Marcus Denker

14382 ----- Issue 5447: Deprecate #methodReferencesInCategory: http://code.google.com/p/pharo/issues/detail?id=5447 Issue 5444: Add a class variable on Morph http://code.google.com/p/pharo/issues/detail?id=5444 Issue 5025: Tests for SystemAnnouncements are not in standalone package http://code.google.com/p/pharo/issues/detail?id=5025 -- Marcus Denker -- http://marcusdenker.de

March 8, 2012

[Pharo-project] Testing Morphic Designer

by HernÃ¡n Morales Durand

Does someone would mind to share a Morphic Designer working image? [*] I've tried to install it in both Squeak 4.3 and Pharo 1.3 without success. Thanks in advance, HernÃ¡n [*] https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki…

March 8, 2012

Re: [Pharo-project] XMLRPC on 1.4 using Zinc

by GermÃ¡n Arduino

Hi: 2012/3/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Mar 7, 2012, at 12:20 AM, GermÃ¡n Arduino wrote: > > > Today I had some free time and tried and really was very simple to adapt > the client to Zinc, I think is already working (need still to publish and > adapt ConfigurationOf*). > > > > Now I'm studying a bit the server to adapt the code to ZnServer and > eliminate Kom. Then xmlrpc could be also shipped in the image in case of > interest. > > We do not need to ship with the image but having a good configuration > published in MetacelloRepository would be definitively a plus. > > ok. About MetacelloRepository, will continue in Squeaksource? or will be moved to ss3? I noted that some packages in ss3 include their own ConfigurationOf in the same repo than the packages. Cheers.

March 8, 2012

Re: [Pharo-project] EPUB view for Pier Books

by Yanni Chiu

On 07/03/12 1:27 PM, Yanni Chiu wrote: > I've only tried it in Pharo-1.4, so let me know of problems on other > platforms. I just tried the latest build from: http://jenkins.lukas-renggli.ch/job/Pier%202/ You should be able navigate to the book in the sample distribution, then look for a view "Book EPUB" and download the .epub file. Then open in an EPUB reader. (Or, in Firefox you can open a new tab, instead of doing the download). The EPUB navigation pane works, but the internal Pier book links (in the table of contents, say) do not work. I'll look into it.

March 8, 2012

Re: [Pharo-project] [Moose-dev] Re: numerical method in smalltalk

by Nicolas Cellier

I just committed a ConfigurationOfSmallapack that loads in Pharo1.4 and passes the tests on MacOSX (use version 1.1 or #development). On other platforms, you'll need to provide appropriate LAPACK/BLAS DLL. In other dialects (Squeak) or Pharo versions, the configuration has not been tested. Nicolas Le 6 mars 2012 12:32, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : > > On Mar 6, 2012, at 3:11 AM, Serge Stinckwich wrote: > > > On Tue, Mar 6, 2012 at 4:29 AM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> It would be really interesting to organize a bit the scientific > packages so that we have one nice library to look for. > >> Serge if you have some code please package it. > > > > Yes sure ! > > > > Anyone is aware of any Smalltalk code/project that might be used for a > > scientific library for Smalltalk. > > At the moment, there is a lot of fragmentation: > > > > - DHBNumerical (MIT): http://www.squeaksource.com/DHBNumerical.html > > - StMath (licence unknown): > > http://live.exept.de/doc/online/english/programming/goody_stmath.html > > - MathComplex and MathQuaternion (MIT): > http://www.squeaksource.com/Complex.html > > - Smallapack (MIT): http://www.squeaksource.com/Smallapack.html > > > > Who is willing to contribue and in what domain (numerical analysis, > > matrix, probability distribution, ...) ? > > > > Maybe we can propose a GSOC project for a student ? > > why not > now we should start to > - define a configurationOf for DHB > - produce more tests Right now they are all in one class > - may be produce some simple doc. I should reread the book (I read > it in draft at least 5 times). > > Stef > > > Regards, > > -- > > Serge Stinckwich > > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > > Every DSL ends up being Smalltalk > > http://doesnotunderstand.org/ > > > > >

March 8, 2012

[Pharo-project] Adding a statement programmatically

by Sean P. DeNigris

What's the easiest way to add a statement to an existing method? In the case I'm thinking about, it's going at the end, so I can cheat and just recompile with the string appended, but I'd like to know how to insert into an arbitrary place in the AST... Thanks. Sean -- View this message in context: http://forum.world.st/Adding-a-statement-programmatically-tp4454447p4454447… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 7, 2012

Re: [Pharo-project] Fuel - class loading issue when superclass changed inst vars

by Eliot Miranda

On Wed, Mar 7, 2012 at 2:10 AM, Frank Shearar <frank.shearar(a)gmail.com>wrote: > On 6 March 2012 22:22, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Frank, > > > > On Tue, Mar 6, 2012 at 1:49 PM, Frank Shearar <frank.shearar(a)gmail.com> > > wrote: > >> > >> On 6 March 2012 18:27, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> > > >> > > >> > On Tue, Mar 6, 2012 at 3:05 AM, Henrik Johansen > >> > <henrik.s.johansen(a)veloxit.no> wrote: > >> >> > >> >> > >> >> On Mar 6, 2012, at 12:03 PM, Henrik Johansen wrote: > >> >> > >> >> >> > >> >> > > >> >> > Parcels > >> >> > - Check a hash based on class layout vs equivalent hash for the > >> >> > stored > >> >> > method's class (stored with the method). > >> >> > If different: > >> >> > 1) check for existence of a backwards-compatability reader method, > >> >> > hand > >> >> > the old instance to it, and expect the old instance to be #become'd > >> >> > into > >> >> > something current, > >> >> > 2) raise an error if no such method exists. > >> >> > > >> >> > Now, the main problem with this scheme is it's left as an exercise > to > >> >> > the user to come up with a procedure to ensure said > backwards-compat > >> >> > reader > >> >> > method stays up to date as additional changes are made. > >> >> > > >> >> > Is it a big problem? > >> >> > Depends on your tests, and programmer diligence at any given day. > >> >> > > >> >> > Added inst vars are not a big deal, as if you forget them, there > will > >> >> > usually be a nil #DNU somewhere down the line. (or you use lazy > >> >> > initialization, and everything works as expected even for existing > >> >> > instances) > >> >> > > >> >> > Removals/reorderings are a bigger issue, as the detection of > failure > >> >> > (inst vars in wrong slots) are often far removed from the source of > >> >> > problems > >> >> > (forgetting to update the reader method), > >> >> > If seldomly used, it may even go unnoticed until the instance is > next > >> >> > saved, at which time you're in real trouble (especially if saved > >> >> > alongside > >> >> > newly created ones, in which case there is no consistency). > >> >> > > >> >> > In general I think it's an ok scheme, but would like to see a > >> >> > solution > >> >> > more resilient to user-error. > >> >> > How to achieve that is an interesting topic, which I haven't yet > >> >> > found > >> >> > time to think through as thoroughly as I had wished/intended some > >> >> > months > >> >> > ago. :( > >> >> > >> >> Errr, BOSS, not Parcels. > >> > > >> > > >> > Right. What Parcels do is shape-change instances *and* rescan methods > to > >> > fix > >> > up inst var offsets. When a parcel is saved the "signature" of > classes > >> > of > >> > instances there-in are saved so that the parcel contains all the inst > >> > var > >> > names of the class and its superclass. If on load the superclass > chain > >> > has > >> > a different set of inst vars then lost inst vars are omitted and added > >> > inst > >> > vars are nil in the materialized instances. If a Parcel contains a > full > >> > class (not just instances) that has methods, and the superclass chains > >> > inst > >> > vars have changed then these methods are "rescanned" (disassembled, > and > >> > reassembled, not using the compiler) and inst var offsets are fixed > up, > >> > missing inst vars getting changed into undeclared variable references > (I > >> > think; at least this is what *should* happen; its what happens when > one > >> > removes an inst var that is still referenced from methods). > >> > > >> > What's missing in the parcel scheme is any hook to allow the user to > >> > process > >> > shape-changing instances with the values of lost inst vars in hand. > >> > Presumably there will be cases when those values are essential to any > >> > schema migration. Personally I would want to decouple schema > migration > >> > and > >> > add it as a post-processing step, which would imply that the > >> > materializer > >> > would offer a service (materialize in a special mode) where it > >> > constructed a > >> > dictionary from materialized and shape-changed instance to in parcel > >> > state > >> > (e.g. an Array of inst var values as they occurred in the parcel). > Then > >> > the > >> > materialized instance could be migrated after the fact, with the > default > >> > behaviour being analogous to what the system does now on class > >> > redefinition > >> > (values of deleted inst vars are lost, aded inst vars are nil). > >> > >> This sounds a bit like CLOS' UPDATE-INSTANCE-FOR-REDEFINED-CLASS [1], > >> which is a generic function (for our purposes just think "something a > >> bit like a method") that you define and is invoked by the machinery > >> involved in changing/redefining classes. > >> > >> A colleague told me about this part of CLOS the other day when > >> discussing class-based OO: it's the sort of thing we need in at least > >> the Browser, so one can change the shape of existing instances and > >> ensure the new class invariants are maintained. > > > > > > But Smalltalk has done without this for 40 years. It has supported > existing > > instance redefinition but no-one has felt the need to provide a scheme > for > > redefinition in the IDE. In any case it is relatively trivial to script > it, > > e.g.: > > > > | instanceState | > > instanceState := IdentityDictionary new. > > myClass allInstancesDo: [:i| instanceState at: i put: ((1 > > to: myClass instSize) collect: [:ivi| i instVarAt: ivi])]. > > myClass superclass subclass: myClass name instanceVariableNames: myClass > > instVarNamesString, ' theExtraInstVar' [...]. > > myClass compile: sourceForupdateToNewFormatFrom. > > myClass allInstancesDo: [:i| i updateToNewFormatFrom: (instanceState at: > i] > > > > So if and when you need it you can roll your own (and I've never needed > it; > > but I have wanted the refactoring browser to preserve inst vars on push > > up/push dwn). > > Indeed, it is trivial. Using #allInstancesDo: is exactly what I used > when my colleague and I were discussing the issue. The only difference > is that _I_ did the migration, not my tools. > > > However, collections of persistent objects are a different kettle of > fish. > > It is much more likely to need instance migration on load, especially > for > > library objects that the user is merely using and whose implementation > has > > evolved over time (e.g. UI elements such as morphs). > > > >> > >> (For instance, for > >> "purely functional" objects, you really don't want to use reflection > >> to initialise new instvars from outside the object.) > > > > > > But the class builder uses an unprotected interface (instVarAt: and > > instVarAt:put:). So this turns out not to be an issue. > > That's exactly to what I was referring: I lump #instVarAt: in the > reflection bucket. I realise its _utility_, but it's strong medicine. > Which is pretty much why you're pushing mirrors, right? So that some > things - the class builder, as an example - can make use of such a > (powerful and dangerous) tool while some random library can't. > Certainly one can't have security and unfettered reflection, and hence mirrors are a way of providing reflection safely. But the complications a full mirror framework introduce shouldn't be underestimated. And how mirrors are made available safely is something I don't yet fully understand. In an IDE setting they're pretty much freely available so for me I'm not convinced of the utility. Deployment is another thing altogether. However, albeit a small point, I do think that light-weight mirror methods like object:instVarAt:put: are the interface the ClassBuilder should use, not instVarAt: on instances. The latter breaks with proxies, and the change from one to the other is pretty trivial. > > frank > > >> So you'd change > >> the class definition, supply a way of handling the schema migration, > >> and then the image would change the class definition and run the > >> migration. > >> > >> frank > >> > >> [1] http://clhs.lisp.se/Body/f_upda_1.htm > >> > >> > This reminds me of a bug with the ClassBuilder/RefactoringBrowser > >> > combination. If one refactors pushing an inst var up to a superclass > or > >> > down to subclasses, the values of te inst var in instances are lost > >> > because > >> > the class change is in fact done as two changes, a deletion followed > by > >> > an > >> > addition. This again could be fixed in a wrapper, building a > dictionary > >> > from instance to values, performing the set of class changes, and then > >> > restoring the inst var state from the dictionary. > >> > > >> > > >> >> > >> >> My bad. > >> >> > >> >> Cheers, > >> >> Henry > >> >> > >> >> > >> > > >> > > >> > > >> > -- > >> > best, > >> > Eliot > >> > > >> > > > > > > > > -- > > best, > > Eliot > > > > -- best, Eliot

March 7, 2012

Re: [Pharo-project] XMLRPC on 1.4 using Zinc

by StÃ©phane Ducasse

On Mar 7, 2012, at 12:20 AM, GermÃ¡n Arduino wrote: > Today I had some free time and tried and really was very simple to adapt the client to Zinc, I think is already working (need still to publish and adapt ConfigurationOf*). > > Now I'm studying a bit the server to adapt the code to ZnServer and eliminate Kom. Then xmlrpc could be also shipped in the image in case of interest. We do not need to ship with the image but having a good configuration published in MetacelloRepository would be definitively a plus. > BTW, very very good code on Zinc, well factored, using patterns, easy to understand, very good job Sven. :)

March 7, 2012

Re: [Pharo-project] Pharo 1.4 Tests-Unix - Build # 272 - Still Unstable!

by Igor Stasenko

On 7 March 2012 17:54, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > The are all failing for the same reason (more or less): > > UTF8TextConverter(Object)>>error: > UTF8TextConverter>>errorMalformedInput > UTF8TextConverter>>nextFromStream: > ByteString(String)>>convertFromWithConverter: > FSFilePluginPrims>>decode: > > UTF8TextConverter(Object)>>error: > UTF8TextConverter>>errorMalformedInput > UTF8TextConverter>>nextFromStream: > ByteString(String)>>convertFromWithConverter: > > I will try on Linux later tonight... > i think i know what is it. see http://code.google.com/p/pharo/issues/detail?id=5445&sort=-id&colspec=ID%20… at least the walkback showing similar sympthoms.. and i even know who to blame... (should bring a butchery knife to the lab ) ;) > On 07 Mar 2012, at 16:46, Marcus Denker wrote: > >> On Mar 7, 2012, at 3:52 PM, Sven Van Caekenberghe wrote: >> >>> Hmm, I downloaded build #322 on which these tests are based (I think), and pharo #14381 passes all Zinc and FS tests, so is this a Linux problem ? >>> >> >> I think so... we are changeing the build server setup, and this now uses another VM... But why so many tests are failing I have no idea. >> >> >>> On 07 Mar 2012, at 15:19, jenkins-pharo.ci.inria.fr(a)jenkins-server.lille.inria.fr wrote: >>> >>>> Â Â BUILD UNSTABLE >>>> Build URL Â https://ci.lille.inria.fr/pharo/job/Pharo%201.4%20Tests-Unix/272/ >>>> Project: Â Â Pharo 1.4 Tests-Unix >>>> Date of build: Â Â Â Wed, 07 Mar 2012 15:14:45 +0100 >>>> Build duration: Â Â 4 mn 26 s >>>> >>>> CHANGES >>>> No Changes >>>> >>>> JUnit Tests >>>> Name: Announcements.Tests.Core Failed: 0 test(s), Passed: 29 test(s), Skipped: 0 test(s), Total: 29 test(s) >>>> Name: BalloonTests.Collections Failed: 0 test(s), Passed: 34 test(s), Skipped: 0 test(s), Total: 34 test(s) >>>> Name: CollectionsTests.Arrayed Failed: 0 test(s), Passed: 560 test(s), Skipped: 0 test(s), Total: 560 test(s) >>>> Name: CollectionsTests.Atomic Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s) >>>> Name: CollectionsTests.Sequenceable Failed: 0 test(s), Passed: 907 test(s), Skipped: 0 test(s), Total: 907 test(s) >>>> Name: CollectionsTests.SplitJoin Failed: 0 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 27 test(s) >>>> Name: CollectionsTests.Stack Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s) >>>> Name: CollectionsTests.Streams Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s) >>>> Name: CollectionsTests.Strings Failed: 0 test(s), Passed: 591 test(s), Skipped: 0 test(s), Total: 591 test(s) >>>> Name: CollectionsTests.Support Failed: 0 test(s), Passed: 12 test(s), Skipped: 0 test(s), Total: 12 test(s) >>>> Name: CollectionsTests.Text Failed: 0 test(s), Passed: 45 test(s), Skipped: 0 test(s), Total: 45 test(s) >>>> Name: CollectionsTests.Unordered Failed: 0 test(s), Passed: 1951 test(s), Skipped: 0 test(s), Total: 1951 test(s) >>>> Name: CollectionsTests.Weak Failed: 0 test(s), Passed: 739 test(s), Skipped: 0 test(s), Total: 739 test(s) >>>> Name: CompilerTests Failed: 0 test(s), Passed: 178 test(s), Skipped: 0 test(s), Total: 178 test(s) >>>> Name: CompressionTests.Archive Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) >>>> Name: FS.Tests.AnsiStreams Failed: 0 test(s), Passed: 40 test(s), Skipped: 0 test(s), Total: 40 test(s) >>>> Name: FS.Tests.Core Failed: 0 test(s), Passed: 169 test(s), Skipped: 0 test(s), Total: 169 test(s) >>>> Name: FS.Tests.Disk Failed: 24 test(s), Passed: 27 test(s), Skipped: 0 test(s), Total: 51 test(s) >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testFileNames >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testFileStreamDo >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testReadStream >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testReadStreamDo >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testReadStreamDoIfAbsent >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testReadStreamIfAbsent >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testWriteStream >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testWriteStreamDo >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testWriteStreamDoIfPresent >>>> â¢ Failed: FS.Tests.Disk.FSDiskFilesystemTest.testWriteStreamIfPresent >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testAt >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testAtPut >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testAtPutBinaryAscii >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testAtWriteBinaryAscii >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testClose >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testCreatedOpen >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testIO >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testReadBufferTooLarge >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testReadOnly >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testReference >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testSizeAfterGrow >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testSizeNoGrow >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testTruncate >>>> â¢ Failed: FS.Tests.Disk.FSFileHandleTest.testWriteStream >>>> Name: FS.Tests.Memory Failed: 0 test(s), Passed: 50 test(s), Skipped: 0 test(s), Total: 50 test(s) >>>> Name: FreeTypeTests.cache Failed: 0 test(s), Passed: 23 test(s), Skipped: 0 test(s), Total: 23 test(s) >>>> Name: Gofer.Tests Failed: 0 test(s), Passed: 45 test(s), Skipped: 0 test(s), Total: 45 test(s) >>>> Name: Graphics.Tests.Files Failed: 0 test(s), Passed: 47 test(s), Skipped: 0 test(s), Total: 47 test(s) >>>> Name: Graphics.Tests.Primitives Failed: 0 test(s), Passed: 57 test(s), Skipped: 0 test(s), Total: 57 test(s) >>>> Name: HelpSystem.Tests.Builders Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) >>>> Name: HelpSystem.Tests.Core.Model Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) >>>> Name: HelpSystem.Tests.Core.UI Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s) >>>> Name: HelpSystem.Tests.Core.Utilities Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) >>>> Name: KernelTests.Chronology Failed: 0 test(s), Passed: 578 test(s), Skipped: 0 test(s), Total: 578 test(s) >>>> Name: KernelTests.Classes Failed: 0 test(s), Passed: 68 test(s), Skipped: 0 test(s), Total: 68 test(s) >>>> Name: KernelTests.Exception Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: KernelTests.Methods Failed: 1 test(s), Passed: 176 test(s), Skipped: 0 test(s), Total: 177 test(s) >>>> â¢ Failed: KernelTests.Methods.MethodContextTest.testClosureRestart >>>> Name: KernelTests.Numbers Failed: 0 test(s), Passed: 265 test(s), Skipped: 0 test(s), Total: 265 test(s) >>>> Name: KernelTests.Objects Failed: 0 test(s), Passed: 86 test(s), Skipped: 0 test(s), Total: 86 test(s) >>>> Name: KernelTests.Pragmas Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: KernelTests.Processes Failed: 0 test(s), Passed: 19 test(s), Skipped: 0 test(s), Total: 19 test(s) >>>> Name: MorphicTests.Basic Failed: 0 test(s), Passed: 16 test(s), Skipped: 0 test(s), Total: 16 test(s) >>>> Name: MorphicTests.Kernel Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) >>>> Name: MorphicTests.Text Support Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) >>>> Name: MorphicTests.Widgets Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: MorphicTests.WindowNotification Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) >>>> Name: Multilingual.Tests.TextConversion Failed: 0 test(s), Passed: 7 test(s), Skipped: 0 test(s), Total: 7 test(s) >>>> Name: NetworkTests.Kernel Failed: 0 test(s), Passed: 31 test(s), Skipped: 0 test(s), Total: 31 test(s) >>>> Name: NetworkTests.Mail Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) >>>> Name: NetworkTests.Protocols Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: NetworkTests.RFC822 Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) >>>> Name: NetworkTests.URI Failed: 0 test(s), Passed: 105 test(s), Skipped: 0 test(s), Total: 105 test(s) >>>> Name: NetworkTests.UUID Failed: 0 test(s), Passed: 14 test(s), Skipped: 0 test(s), Total: 14 test(s) >>>> Name: NetworkTests.Url Failed: 0 test(s), Passed: 42 test(s), Skipped: 0 test(s), Total: 42 test(s) >>>> Name: Regex.Tests.Core Failed: 0 test(s), Passed: 188 test(s), Skipped: 0 test(s), Total: 188 test(s) >>>> Name: Ring.Tests.Containers Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) >>>> Name: Ring.Tests.Kernel Failed: 0 test(s), Passed: 61 test(s), Skipped: 0 test(s), Total: 61 test(s) >>>> Name: SUnit.Core.Extensions Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: SUnit.Core.Utilities Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: SUnit.Tests.Core Failed: 0 test(s), Passed: 77 test(s), Skipped: 0 test(s), Total: 77 test(s) >>>> Name: ShoutTests.Parsing Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) >>>> Name: ShoutTests.Styling Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) >>>> Name: SystemAnnouncements.Tests Failed: 0 test(s), Passed: 51 test(s), Skipped: 0 test(s), Total: 51 test(s) >>>> Name: Tests.Browser Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) >>>> Name: Tests.Bugs Failed: 0 test(s), Passed: 25 test(s), Skipped: 0 test(s), Total: 25 test(s) >>>> Name: Tests.Compression Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s) >>>> Name: Tests.Digital Signatures Failed: 0 test(s), Passed: 8 test(s), Skipped: 0 test(s), Total: 8 test(s) >>>> Name: Tests.Exceptions Failed: 0 test(s), Passed: 28 test(s), Skipped: 0 test(s), Total: 28 test(s) >>>> Name: Tests.Files Failed: 9 test(s), Passed: 48 test(s), Skipped: 0 test(s), Total: 57 test(s) >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testDeleteDirectory >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testDirectoryExists >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testDirectoryExistsWhenLikeNamedFileExists >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testExists >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testNonExistentDirectory >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testOldFileOrNoneNamed >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testRecursiveMatching >>>> â¢ Failed: Tests.Files.FileDirectoryTest.testSimpleMatching >>>> â¢ Failed: Tests.Files.FileStreamTest.testPositionPastEndIsAtEnd >>>> Name: Tests.Finalization Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) >>>> Name: Tests.Localization Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) >>>> Name: Tests.Monticello Failed: 4 test(s), Passed: 116 test(s), Skipped: 0 test(s), Total: 120 test(s) >>>> â¢ Failed: Tests.Monticello.MCDirectoryRepositoryTest.testAddAndLoad >>>> â¢ Failed: Tests.Monticello.MCDirectoryRepositoryTest.testIncludesName >>>> â¢ Failed: Tests.Monticello.MCDirectoryRepositoryTest.testLoadMissingNode >>>> â¢ Failed: Tests.Monticello.MCDirectoryRepositoryTest.testStoreAndLoad >>>> Name: Tests.Multilingual Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Tests.Object Events Failed: 0 test(s), Passed: 24 test(s), Skipped: 0 test(s), Total: 24 test(s) >>>> Name: Tests.ObjectsAsMethods Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Tests.PackageInfo Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) >>>> Name: Tests.Polymorph.Widgets Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) >>>> Name: Tests.Release Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Tests.ScriptLoader Failed: 0 test(s), Passed: 4 test(s), Skipped: 0 test(s), Total: 4 test(s) >>>> Name: Tests.System Failed: 0 test(s), Passed: 271 test(s), Skipped: 0 test(s), Total: 271 test(s) >>>> Name: Tests.SystemChangeNotification Failed: 0 test(s), Passed: 37 test(s), Skipped: 0 test(s), Total: 37 test(s) >>>> Name: Tests.SystemHistory Failed: 0 test(s), Passed: 14 test(s), Skipped: 0 test(s), Total: 14 test(s) >>>> Name: Tests.SystemSupport Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) >>>> Name: Tests.TextEditors Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Tests.Traits Failed: 0 test(s), Passed: 56 test(s), Skipped: 0 test(s), Total: 56 test(s) >>>> Name: Tests.Traits.MOP Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Tests.VM Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s) >>>> Name: ToolsTest.Base Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s) >>>> Name: ToolsTest.Debugger Failed: 0 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 10 test(s) >>>> Name: ToolsTest.Finder Failed: 0 test(s), Passed: 9 test(s), Skipped: 0 test(s), Total: 9 test(s) >>>> Name: ToolsTest.Inspector Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s) >>>> Name: ToolsTest.MessageTally Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s) >>>> Name: ToolsTest.PointerFinder Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s) >>>> Name: Zinc.Tests Failed: 1 test(s), Passed: 200 test(s), Skipped: 0 test(s), Total: 201 test(s) >>>> â¢ Failed: Zinc.Tests.ZnClientTests.testPostMultipart >>>> >>>> >>> >> > -- Best regards, Igor Stasenko.

March 7, 2012

Re: [Pharo-project] Test

by Igor Stasenko

On 7 March 2012 20:04, Ulysse <pharo.ulysse(a)gmail.com> wrote: > This is a test for the generating mail script :) > > > Thanks to ignore this, > Ulysse, the integrator from outer space monkey? :) -- Best regards, Igor Stasenko.

March 7, 2012