- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Tests Gueard report for 20144

by StÃ©phane Ducasse

marcus do you know if it has the latest vm with the fix for files primitives? stef On Jun 21, 2012, at 9:36 AM, Marcus Denker wrote: > > On Jun 21, 2012, at 9:31 AM, StÃ©phane Ducasse wrote: > >> Hi pavel >> >> where did you run the tests >> > > on the build server. > > https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0-Tests/Archit… > > > > -- > Marcus Denker -- http://marcusdenker.de > >

June 21, 2012

Re: [Pharo-project] Tests Gueard report for 20144

by Marcus Denker

On Jun 21, 2012, at 9:31 AM, StÃ©phane Ducasse wrote: > Hi pavel > > where did you run the tests > on the build server. https://ci.lille.inria.fr/pharo/view/Pharo%202.0/job/Pharo-2.0-Tests/Archit… -- Marcus Denker -- http://marcusdenker.de

June 21, 2012

Re: [Pharo-project] Tests Gueard report for 20144

by StÃ©phane Ducasse

Hi pavel where did you run the tests because sunday all the zip tests where green when we finished to work with camillo. Stef On Jun 21, 2012, at 9:10 AM, Pavel Krivanek wrote: > Tests Gueard report for 20144 > http://code.google.com/p/pharo/wiki/TestsGuard > > Because the Pharo job and the test job were broken for some time, this > report collects several updates. We have no platform dependent test > failure again. A lot of thests is now green but we have some new > failures. > > Fixed tests: > * CompressionTests.Archive.ZipArchiveTest.testAddNonExistentFile > * CompressionTests.Archive.ZipArchiveTest.testDate29Feb2000 > * CompressionTests.Archive.ZipArchiveTest.testPackDate > * CompressionTests.Archive.ZipArchiveTest.testPackTime > * CompressionTests.Archive.ZipArchiveTest.testSetLastModification > * CompressionTests.Archive.ZipArchiveTest.testUnpackDate > * CompressionTests.Archive.ZipArchiveTest.testUnpackTime > * FileSystem.Tests.Core.FileReferenceTest.testRename > * FileSystem.Tests.Disk.DiskFileSystemTest.testCreateDirectoryNoParent > * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectory > * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectoryCreatesParent > * FileSystem.Tests.Disk.DiskFileSystemTest.testFileNames > * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamDoIfAbsent > * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamIfAbsent > * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamDoIfPresent > * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamIfPresent > * FileSystem.Tests.Disk.FileHandleTest.testEnsureClosed > * Graphics.Tests.Files.PNGReadWriterTest.test1BitColors > * Graphics.Tests.Files.PNGReadWriterTest.test2BitColors > * Graphics.Tests.Files.PNGReadWriterTest.test4BitColors > * Graphics.Tests.Files.PNGReadWriterTest.test8BitColors > * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBasicChunk > * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBinaryUpTo > * Tests.System.CommandLine.BasicCodeLoaderTest.testInstallSourceFilesFail > * CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNames > * CompressionTests.Archive.ZipArchiveTest.testFilePermissions > * CompressionTests.Archive.ZipArchiveTest.testZip > * FileSystem.Tests.Disk.DiskFileSystemTest.testRootIsNotAFile > * Gofer.Tests.GoferApiTest.testDirectoryRepository > * Gofer.Tests.GoferApiTest.testSubDirectoryRepository > > New failures: > * Tests.Monticello.MCDirectoryRepositoryTest.testIncludesName > * Tests.Monticello.MCDirectoryRepositoryTest.testStoreAndLoad > * Tests.Monticello.MCWorkingCopyTest.testAncestorMerge > * Tests.Monticello.MCWorkingCopyTest.testBackport > * Tests.Monticello.MCWorkingCopyTest.testDoubleRepeatedMerge > * Tests.Monticello.MCWorkingCopyTest.testMergeIntoImageWithNoChanges > * Tests.Monticello.MCWorkingCopyTest.testMergeIntoUnmodifiedImage > * Tests.Monticello.MCWorkingCopyTest.testNaming > * Tests.Monticello.MCWorkingCopyTest.testOptimizedLoad > * Tests.Monticello.MCWorkingCopyTest.testRedundantMerge > * Tests.Monticello.MCWorkingCopyTest.testRepeatedMerge > * Tests.Monticello.MCWorkingCopyTest.testRepositoryFallback > * Tests.Monticello.MCWorkingCopyTest.testSelectiveBackport > * Tests.Monticello.MCWorkingCopyTest.testSimpleMerge > * Tests.Monticello.MCWorkingCopyTest.testSnapshotAndLoad > * Tests.Release.ReleaseTest.testObsoleteClasses > > -- Pavel >

June 21, 2012

[Pharo-project] Tests Gueard report for 20144

by Pavel Krivanek

Tests Gueard report for 20144 http://code.google.com/p/pharo/wiki/TestsGuard Because the Pharo job and the test job were broken for some time, this report collects several updates. We have no platform dependent test failure again. A lot of thests is now green but we have some new failures. Fixed tests: * CompressionTests.Archive.ZipArchiveTest.testAddNonExistentFile * CompressionTests.Archive.ZipArchiveTest.testDate29Feb2000 * CompressionTests.Archive.ZipArchiveTest.testPackDate * CompressionTests.Archive.ZipArchiveTest.testPackTime * CompressionTests.Archive.ZipArchiveTest.testSetLastModification * CompressionTests.Archive.ZipArchiveTest.testUnpackDate * CompressionTests.Archive.ZipArchiveTest.testUnpackTime * FileSystem.Tests.Core.FileReferenceTest.testRename * FileSystem.Tests.Disk.DiskFileSystemTest.testCreateDirectoryNoParent * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectory * FileSystem.Tests.Disk.DiskFileSystemTest.testEnsureDirectoryCreatesParent * FileSystem.Tests.Disk.DiskFileSystemTest.testFileNames * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamDoIfAbsent * FileSystem.Tests.Disk.DiskFileSystemTest.testReadStreamIfAbsent * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamDoIfPresent * FileSystem.Tests.Disk.DiskFileSystemTest.testWriteStreamIfPresent * FileSystem.Tests.Disk.FileHandleTest.testEnsureClosed * Graphics.Tests.Files.PNGReadWriterTest.test1BitColors * Graphics.Tests.Files.PNGReadWriterTest.test2BitColors * Graphics.Tests.Files.PNGReadWriterTest.test4BitColors * Graphics.Tests.Files.PNGReadWriterTest.test8BitColors * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBasicChunk * Multilingual.Tests.TextConversion.MultiByteFileStreamTest.testBinaryUpTo * Tests.System.CommandLine.BasicCodeLoaderTest.testInstallSourceFilesFail * CompressionTests.Archive.ZipArchiveTest.testCreateWithRelativeNames * CompressionTests.Archive.ZipArchiveTest.testFilePermissions * CompressionTests.Archive.ZipArchiveTest.testZip * FileSystem.Tests.Disk.DiskFileSystemTest.testRootIsNotAFile * Gofer.Tests.GoferApiTest.testDirectoryRepository * Gofer.Tests.GoferApiTest.testSubDirectoryRepository New failures: * Tests.Monticello.MCDirectoryRepositoryTest.testIncludesName * Tests.Monticello.MCDirectoryRepositoryTest.testStoreAndLoad * Tests.Monticello.MCWorkingCopyTest.testAncestorMerge * Tests.Monticello.MCWorkingCopyTest.testBackport * Tests.Monticello.MCWorkingCopyTest.testDoubleRepeatedMerge * Tests.Monticello.MCWorkingCopyTest.testMergeIntoImageWithNoChanges * Tests.Monticello.MCWorkingCopyTest.testMergeIntoUnmodifiedImage * Tests.Monticello.MCWorkingCopyTest.testNaming * Tests.Monticello.MCWorkingCopyTest.testOptimizedLoad * Tests.Monticello.MCWorkingCopyTest.testRedundantMerge * Tests.Monticello.MCWorkingCopyTest.testRepeatedMerge * Tests.Monticello.MCWorkingCopyTest.testRepositoryFallback * Tests.Monticello.MCWorkingCopyTest.testSelectiveBackport * Tests.Monticello.MCWorkingCopyTest.testSimpleMerge * Tests.Monticello.MCWorkingCopyTest.testSnapshotAndLoad * Tests.Release.ReleaseTest.testObsoleteClasses -- Pavel

June 21, 2012

Re: [Pharo-project] [update 2.0] #20145

by Pavel Krivanek

This update significantly breaks the PharoKernel generation because classes in categories Text-Edition and Text-Scanning categories cannot be in this image. Please reject and rollback this update. We need to split the package into three (Text-Core, Text-Edition, Text-Scanning) and check extension methods ownership. We need working PharoKernel for work on related jobs. Cheers, -- Pavel On Wed, Jun 20, 2012 at 6:21 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > 20145 > ----- > > Issue 5945: Â Â Nice packaging for Text stuff > Â Â Â Â http://code.google.com/p/pharo/issues/detail?can=2&q=5945 >

June 21, 2012

Re: [Pharo-project] What happened to smallharbour ?

by garduino

Sorry, this means that the problems I reported in February are solved? I don't tried, honestly I remainded awaiting your comments. Cheers. -- View this message in context: http://forum.world.st/What-happened-to-smallharbour-tp4635752p4635787.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Chris Cunningham

In Monitcello days (and browser), there is Delete working package, and Unload package. I suspect deletePackageNamed: is all about removing the idea of the package, but not the code (as you found) - just making the code part of the image and not a package. You want something like unloadPackage: or #unloadPackage to remove the code (and package) from the system. Assuming that is still there, that is (I don't have a version 2.0 yet). Wouldn't your drive to package everything make you want to guard against the deletePackageNamed: behaviour? Only delete it if there is no code associated to the package, otherwise complain somehow. -Chris

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Fernando Olivero

Seems that removing a package does not imply removing the included classes?Maybe this should be changed? With RPackage is understandable, since its just a layer on top of the system.You have to explicitly register/deregister packages. Fernando On Wed, Jun 20, 2012 at 10:24 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > well, I don't know what the hell happened, but a workaround I think it is > > DataStream removeFromSystem. > RPackageOrganizer Â default unregisterPackageNamed: #'System-Object Storage'. > > On Wed, Jun 20, 2012 at 10:19 PM, Mariano Martinez Peck <marianopeck(a)gmail.com<mailto:marianopeck@gmail.com>> wrote: > So removing 'System-Object Storage' didn't work. I did: > > ScriptLoader new deletePackageNamed: 'System-Object Storage'. > > Now the MCWorkingCopy is removed (I don't see the package in Monticello Browser), but I can still browse the class DataStream, and the package is available from Nautilus. > > Now if I do: > > RPackageOrganizer Â default unregisterPackageNamed: #'System-Object Storage' > > I don't see the package in Nautilus, but the class "DataStream" is still alive. I can do "DataStream name -> #DataStream" ..et...when I browse it with Nautilus I don't see the class but the category _UnpackagedPackage.. > > so...how the hell can I remove this package and class from everywhere in the system? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 20, 2012

Re: [Pharo-project] How to correctly remove a package for everywhere?

by Mariano Martinez Peck

well, I don't know what the hell happened, but a workaround I think it is DataStream removeFromSystem. RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage'. On Wed, Jun 20, 2012 at 10:19 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > So removing 'System-Object Storage' didn't work. I did: > > ScriptLoader new deletePackageNamed: 'System-Object Storage'. > > Now the MCWorkingCopy is removed (I don't see the package in Monticello > Browser), but I can still browse the class DataStream, and the package is > available from Nautilus. > > Now if I do: > > RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage' > > I don't see the package in Nautilus, but the class "DataStream" is still > alive. I can do "DataStream name -> #DataStream" ..et...when I browse it > with Nautilus I don't see the class but the category _UnpackagedPackage.. > > so...how the hell can I remove this package and class from everywhere in > the system? > > thanks > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

June 20, 2012

[Pharo-project] How to correctly remove a package for everywhere?

by Mariano Martinez Peck

So removing 'System-Object Storage' didn't work. I did: ScriptLoader new deletePackageNamed: 'System-Object Storage'. Now the MCWorkingCopy is removed (I don't see the package in Monticello Browser), but I can still browse the class DataStream, and the package is available from Nautilus. Now if I do: RPackageOrganizer default unregisterPackageNamed: #'System-Object Storage' I don't see the package in Nautilus, but the class "DataStream" is still alive. I can do "DataStream name -> #DataStream" ..et...when I browse it with Nautilus I don't see the class but the category _UnpackagedPackage.. so...how the hell can I remove this package and class from everywhere in the system? thanks -- Mariano http://marianopeck.wordpress.com

June 20, 2012