- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by David T. Lewis

On Fri, Jul 06, 2012 at 04:49:35PM -0400, DeNigris Sean wrote: > The few that I checked had to do with stdout being closed... > > OSProcess-dtl.70 > Mac Lion > Also tried running with vm from command line > > cc/ David Lewis OSProcess and CommandShell tests run successfully on Pharo 1.4 with an interpreter VM on Linux. Many of the tests rely on #forkSqueak to set up the test conditions, and these tests may not run on VMs that cannot fully support #forkSqueak (which is tricky to do when pthreads are involved in the VM). But note that the test failures do not mean that e.g. file locking is broken, they just mean that the file locking tests will not succeed if forkSqueak is not available on the platform. There might be some plugin version issues too. The testRedirectStdOutTo failure happened only when I ran the test on a Cog VM so I suspect this may reflect an out of date plugin. Sorry I cannot check now to be sure, but the failure happens with this version: OSProcess accessor osppModuleVersionString ==> '4.3.3 Cog' And no failure with this: OSProcess accessor osppModuleVersionString ==> '4.4.11' Dave > > UnixProcessAccessorTestCase>>#testRedirectStdOutTo > UnixProcessTestCase>>#testCatAFile > UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDo > UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDoThenQuit > UnixProcessTestCase>>#testClassForkSqueak > UnixProcessTestCase>>#testClassForkSqueakAndDo > UnixProcessTestCase>>#testClassForkSqueakAndDoThenQuit > UnixProcessTestCase>>#testForkHeadlessSqueakAndDo > UnixProcessTestCase>>#testForkHeadlessSqueakAndDoThenQuit > UnixProcessTestCase>>#testForkSqueak > UnixProcessTestCase>>#testForkSqueakAndDo > UnixProcessTestCase>>#testForkSqueakAndDoThenQuit > UnixProcessTestCase>>#testHeadlessChild > UnixProcessTestCase>>#testRunCommand > UnixProcessTestCase>>#testSpawnTenHeadlessChildren > UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses01 > UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses02 > UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses03 > UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses04 > UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses05 > UnixProcessUnixFileLockingTestCase>>#testFailFileLockOnLockedFile > UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedOverlappedRegion > UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedRegion > UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedSupersetRegion > UnixProcessUnixFileLockingTestCase>>#testFailRegionLockOnLockedFile > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite01 > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite02 > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite03 > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite04 > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite05 > UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite06 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead01 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead02 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite01 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite02 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite03 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite04 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite05 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite06 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite07 > UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite08 > UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions > UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion > UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses01 > UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses02 > UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses03 > UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses04 > UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses05 > UnixProcessWin32FileLockingTestCase>>#testFailFileLockOnLockedFile > UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedOverlappedRegion > UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedRegion > UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedSupersetRegion > UnixProcessWin32FileLockingTestCase>>#testFailRegionLockOnLockedFile > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite01 > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite02 > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite03 > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite04 > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite05 > UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite06 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead01 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead02 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite01 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite02 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite03 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite04 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite05 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite06 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite07 > UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite08 > UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions > UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion

July 7, 2012

[Pharo-project] [update 2.0] #20192

by Marcus Denker

20192 ----- Issue 6296: remove some debugging leftovers http://code.google.com/p/pharo/issues/detail?id=6296 Issue 6294: Update improvement 2 http://code.google.com/p/pharo/issues/detail?id=6294 Issue 5992: testMethodsWithUnboundGlobals http://code.google.com/p/pharo/issues/detail?id=5992 -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

Re: [Pharo-project] Bogus/Annoying #logCr's

by Marcus Denker

On Jul 6, 2012, at 9:10 PM, Sven Van Caekenberghe wrote: > Probably leftovers from debugging: > > AbstractNautilusUI>>mcWorkingCopyCreated: > | package rpackage mcPackage | > 'Passed there' logCr. > window ifNil: [^ self ]. > window isDisplayed ifFalse: [ ^ self ]. > > ... > > RPackageOrganizer>>systemClassRemovedActionFrom: > "A class has been removed, we should update the package adequately." > > | class className rPackage categoryName | > 'herrrrrre ' logCr. > class := ann removedClass. > > â¦ > http://code.google.com/p/pharo/issues/detail?id=6296 -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

Re: [Pharo-project] Google Code labels/templates

by Marcus Denker

On Jul 6, 2012, at 7:35 PM, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> >>> So, now that I said all that, it seems the most powerful/flexible >>> approach >>> would be to leave the "nautilus" tag, remove the leading "Type-" from >>> "Type-[Jenkins|Spec|Seed]", and then to make templates for >>> Jenkins/Spec/Seed >>> like the one for Nautilus. >>> >>> What do you think? >> >> honestly I don't care... there is so much to do that I can't even think >> about details like >> this. >> > > If you give me access, I will take care of it. These clarifications will > avoid more, possibly invalid, issues from cluttering up our minds. That is a great idea! I will add you as and admin. Marcus -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

[Pharo-project] OSProcess test failures in Pharo 1.4

by DeNigris Sean

The few that I checked had to do with stdout being closed... OSProcess-dtl.70 Mac Lion Also tried running with vm from command line cc/ David Lewis UnixProcessAccessorTestCase>>#testRedirectStdOutTo UnixProcessTestCase>>#testCatAFile UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDo UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDoThenQuit UnixProcessTestCase>>#testClassForkSqueak UnixProcessTestCase>>#testClassForkSqueakAndDo UnixProcessTestCase>>#testClassForkSqueakAndDoThenQuit UnixProcessTestCase>>#testForkHeadlessSqueakAndDo UnixProcessTestCase>>#testForkHeadlessSqueakAndDoThenQuit UnixProcessTestCase>>#testForkSqueak UnixProcessTestCase>>#testForkSqueakAndDo UnixProcessTestCase>>#testForkSqueakAndDoThenQuit UnixProcessTestCase>>#testHeadlessChild UnixProcessTestCase>>#testRunCommand UnixProcessTestCase>>#testSpawnTenHeadlessChildren UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses01 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses02 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses03 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses04 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses05 UnixProcessUnixFileLockingTestCase>>#testFailFileLockOnLockedFile UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedOverlappedRegion UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedRegion UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedSupersetRegion UnixProcessUnixFileLockingTestCase>>#testFailRegionLockOnLockedFile UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite01 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite02 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite03 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite04 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite05 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite06 UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead01 UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead02 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite01 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite02 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite03 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite04 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite05 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite06 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite07 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite08 UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses01 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses02 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses03 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses04 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses05 UnixProcessWin32FileLockingTestCase>>#testFailFileLockOnLockedFile UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedOverlappedRegion UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedRegion UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedSupersetRegion UnixProcessWin32FileLockingTestCase>>#testFailRegionLockOnLockedFile UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite01 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite02 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite03 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite04 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite05 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite06 UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead01 UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead02 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite01 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite02 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite03 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite04 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite05 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite06 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite07 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite08 UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion

July 6, 2012

[Pharo-project] Cairo, VM?

by Hilaire Fernandes

Hello, Are there VM ready for Cairo? If so for which system? Hilaire -- Dr. Geo -- http://www.drgeo.eu

July 6, 2012

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

by Sven Van Caekenberghe

On 06 Jul 2012, at 17:06, Marcus Denker wrote: > Issue 6280: NonInteractiveTranscript streams do not survive restarts > http://code.google.com/p/pharo/issues/detail?id=6280 Tested in my server image and it works as expected.

July 6, 2012

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

by Sven Van Caekenberghe

On 06 Jul 2012, at 16:05, Marcus Denker wrote: > Issue 6278: snapshot:andQuit: does no long return if resuming > http://code.google.com/p/pharo/issues/detail?id=6278 I just tested and it works again as before, Thx!

July 6, 2012

Re: [Pharo-project] getting ready to summer release of 1.4

by phil＠highoctane.be

I see it! Thx. 2012/7/6 Sven Van Caekenberghe <sven(a)beta9.be> > > On 06 Jul 2012, at 18:49, Sean P. DeNigris wrote: > > > Already done a few days ago :) > > > http://www.squeaksource.com/MetacelloRepository/ConfigurationOfSton-SeanDeN… > > Thanks (again), Sean ! > You should leave the easy configurations for me, you can do the hard ones. > > @Philippe: > > I copied metacello configs to the necessary places for 1.3, 1.4 and 2.0 > > Sven > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > > > -- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges Belgium

July 6, 2012

[Pharo-project] Bogus/Annoying #logCr's

by Sven Van Caekenberghe

Probably leftovers from debugging: AbstractNautilusUI>>mcWorkingCopyCreated: | package rpackage mcPackage | 'Passed there' logCr. window ifNil: [^ self ]. window isDisplayed ifFalse: [ ^ self ]. ... RPackageOrganizer>>systemClassRemovedActionFrom: "A class has been removed, we should update the package adequately." | class className rPackage categoryName | 'herrrrrre ' logCr. class := ann removedClass. â¦ Sven

July 6, 2012