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

Re: [Pharo-project] failing FS tests
by Marcus Denker March 8, 2012

March 8, 2012

On Mar 8, 2012, at 9:28 AM, Pavel Krivanek wrote: > On Thu, Mar 8, 2012 at 9:18 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> On Mar 8, 2012, at 9:16 AM, Pavel Krivanek wrote: >> >>> On Thu, Mar 8, 2012 at 9:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>>> Hi Marcus, >>>> >>>> there is a lot of new FS failing tests in the update 14381 (also after >>>> re-run). Because this tests are not failing on my local machine, I >>>> guess the reason is in a strange file named test-ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ in the >>>> workspace. I suggest to try to clear workspace before the new build. >>>> >>>> -- Pavel >>> >>> >>> I tried to do that but it failed because of Jenkins error. I guess >>> someone will have to do it manually. >> >> >> I removed the file. It's a file with umlauts in the name... I wonder if it's generated by >> a test? >> > > It seems that FSFilesystemTest testFileNamed creates it. However it is > a quite old method. Was there any change in the CI setup (another VM > version or so)? > Yes, we updated the VM form an old unix interpreter to the recent Cog build by the integration server... (which again shows: there are no trivialities... especially the "simple" stuff that is "not important" is acually failing very often when you then try to do it...) -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] failing FS tests
by Pavel Krivanek March 8, 2012

March 8, 2012

Hi Marcus, there is a lot of new FS failing tests in the update 14381 (also after re-run). Because this tests are not failing on my local machine, I guess the reason is in a strange file named test-ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ in the workspace. I suggest to try to clear workspace before the new build. -- Pavel

1 1

[Pharo-project] Pharo 1.4 Tests-Unix - Build # 274 - Still Unstable!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr March 8, 2012

March 8, 2012

1 0

[Pharo-project] [update 1.4] #14382
by Marcus Denker March 8, 2012

March 8, 2012

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

1 0

[Pharo-project] Testing Morphic Designer
by HernÃ¡n Morales Durand March 8, 2012

March 8, 2012

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…

1 0

Re: [Pharo-project] Fuel - class loading issue when superclass changed inst vars
by Henrik Johansen March 7, 2012

March 7, 2012

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. My bad. Cheers, Henry

6 8

Re: [Pharo-project] Pharo 1.4 Tests-Unix - Build # 272 - Still Unstable!
by Marcus Denker March 7, 2012

March 7, 2012

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 >> >> > -- Marcus Denker -- http://marcusdenker.de

3 3

[Pharo-project] Test
by Ulysse March 7, 2012

March 7, 2012

This is a test for the generating mail script :) Thanks to ignore this, Ulysse, the integrator from outer space

2 1

Re: [Pharo-project] .changes are now 37MBâ¦.
by Marcus Denker March 7, 2012

March 7, 2012

On Mar 6, 2012, at 7:30 PM, Max Leske wrote: > This may be a stupid questionâ¦ (As far as I understand, condensing the changes is not the same) > Why don't you increment the version number of the sources file to 1.1 and use a fresh changes file? > The sources file does not contain the sources and the changes just the changes. (even though one could think so taking the names into account.) The sources file containes the sources of ages ago (1.0), the .changes is "on top of that". This means that the .sources file contains a lot of code from classes and methods that have been removed (like the changes), as well as old versions. The .sources/.changes mechanism merges three responsabilties: 1) be a log of all edited code in case of a crash 2) store the current source of the methods (when you ask a method for code, it reads either from the .sources (method not changed since 1.0) or from the .changes (method was changed). 3) provide a history for all code And all that in 2 big files that one can only append to because? No idea, actually... I personally think that it is a mistake today to merge all these into one such basic mechanism. Especialy if you look at how complex the code is in the image... it's actually amazing. When you do a #condenseSources (which is sadly broken right now), then it generates a .sources file with just the code in the current image. It would be interesting to see how large that is. Marcus -- Marcus Denker -- http://marcusdenker.de

6 9

[Pharo-project] Smalltalk as embedded platform/language?
by Igor Stasenko March 7, 2012

March 7, 2012

It is very long post, so i decided to put it on my blog. http://computeradventures.wordpress.com/ i more or less realizing the scale of changes in order to achieve it, but i also wonder why we do not pay attention to this aspect.. maybe i miss something, maybe we don't need it at all. or maybe there's less painful alternatives... -- Best regards, Igor Stasenko.

5 8