- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60221 Home: https://github.com/pharo-project/pharo-core

Sept. 14, 2016

[pharo-project/pharo-core] 24f358: 60221

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 24f358d5f31ab615454e0bbd7f82ca0f0bb47758 https://github.com/pharo-project/pharo-core/commit/24f358d5f31ab615454e0bbd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-14 (Wed, 14 Sep 2016) Changed paths: M Kernel-Tests.package/ProcessSpecificTest.class/instance/testing/testInheritingExecutionEnvironment.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui buttons/buildBrowseVariablesButton.st M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/browseVariableReferences.st M Refactoring-Tests-Environment.package/RBBrowserEnvironmentTest.class/instance/testing-environments/testAndEnvironment.st M SUnit-Core.package/TestExecutionEnvironment.class/instance/initialization/initialize.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60220.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60221.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60220.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60221.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60221 19087 Tracking of processes during test run should not keep processes strongly. https://pharo.fogbugz.com/f/cases/19087 18755 Variable-button raises "SubscriptOutOfBounds: 1" when a Trait is selected https://pharo.fogbugz.com/f/cases/18755 17543 VM crash in Windows when compiling many symbols https://pharo.fogbugz.com/f/cases/17543 http://files.pharo.org/image/60/60221.zip

Sept. 14, 2016

Re: [Pharo-dev] [Pharo 6] failing tests down to 6

by Ben Coman

Cool to hear this progress. cheers -ben On Wed, Sep 14, 2016 at 1:51 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> With these, we are down to 9 failing tests on the CI: >> > We are down to 6! These: > > > SmalllintManifestCheckerTest.testCriticsOf > SmalllintManifestCheckerTest.testToDoOf > - tests need to be updated, will be fixed with next QA update > > ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits > - fixed upstream > > SystemAnnouncerLiveTest.testNoDeadSubscriptions > Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions > > ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription > #iconNamed: in ClassDescription. > > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by Nicolai Hess

2016-09-13 21:00 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi nicolai > > Why we should not accept > > foo > <func: (3+4) res:0> > ^ self > > and be forced to put around '' > > foo > < func: '(3+4)' res: 0 > > ^ self > > I understand that we store literal but why you do not like it :). > First of all, the old compiler did not accept this. And I am a bit sensitive about changes, we allow a different syntax just because RB happens to allow this (and maybe no one knows why or it just does not happens on purpose). And another reason, even without my fix, if we don't put quotes around that expression, the reformatting the source will convert this to: foo <func: #(3 #+ 4) res: 0> ^ self And, even if (3+4) looks like an expression, it is just a list of literals something like this: foo <func: ([[[}}}) res:0> ^ self would be allowed too. But of course this is only my own opinion :) We can change it back and maybe add support for the reformatter to not convert it to the literal array #(3 #+ 4) . nicolai > Stef > > > 60220 >> 19086 do not allow expressions as pragma arguments >> https://pharo.fogbugz.com/f/cases/19086 >> > > >

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] edd9f3: 60220

by stepharo

Hi nicolai Why we should not accept foo <func: (3+4) res:0> ^ self and be forced to put around '' foo < func: '(3+4)' res: 0 > ^ self I understand that we store literal but why you do not like it :). Stef > 60220 > 19086 do not allow expressions as pragma arguments > https://pharo.fogbugz.com/f/cases/19086

Sept. 13, 2016

[Pharo 6] failing tests down to 6

by Marcus Denker

> > With these, we are down to 9 failing tests on the CI: > We are down to 6! These: SmalllintManifestCheckerTest.testCriticsOf SmalllintManifestCheckerTest.testToDoOf - tests need to be updated, will be fixed with next QA update ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits - fixed upstream SystemAnnouncerLiveTest.testNoDeadSubscriptions Announcements.Tests.Core.Tests.WeakAnnouncerTest.testNoDeadWeakSubscriptions ClassDescriptionTest.testClassDescriptionRespectsPolymorphismWithTraitDescription #iconNamed: in ClassDescription.

Sept. 13, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60220 Home: https://github.com/pharo-project/pharo-core

Sept. 13, 2016

[pharo-project/pharo-core] edd9f3: 60220

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: edd9f3770d89ef3c48592411b97507dcb453bcef https://github.com/pharo-project/pharo-core/commit/edd9f3770d89ef3c48592411… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-09-13 (Tue, 13 Sep 2016) Changed paths: M AST-Core.package/RBParser.class/instance/private-parsing/parsePragmaLiteral.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testInvalidPragmaPosition.st R AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testInvalidPragmas.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testPragmaImplicitLiteralArrayIsInvalid.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60219.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60220.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60219.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60220.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60220 19086 do not allow expressions as pragma arguments https://pharo.fogbugz.com/f/cases/19086 http://files.pharo.org/image/60/60220.zip

Sept. 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] d6bfc8: 60219

by Marcus Denker

Hi, This update should fix the âload updatesâ menu. Thanks to Norbert who helped tracking that down. Marcus > On 13 Sep 2016, at 18:55, GitHub <noreply(a)github.com> wrote: > > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: d6bfc88a219ec6f709fa6d481aa7c83c27089dbc > https://github.com/pharo-project/pharo-core/commit/d6bfc88a219ec6f709fa6d48… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-09-13 (Tue, 13 Sep 2016) > > Changed paths: > M Kernel-Tests.package/MetaclassTest.class/instance/tests/testMetaclassAndTraitClassRespectsPolymorphismRules.st > A Kernel.package/Metaclass.class/instance/instance creation/newAnonymousSubclass.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60218.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60219.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60218.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60219.st > M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st > > Log Message: > ----------- > 60219 > 17857 newAnonymousSubclass should works for Metaclass > https://pharo.fogbugz.com/f/cases/17857 > > 19082 The tool to do updates is broken due to space in SystemVersion > https://pharo.fogbugz.com/f/cases/19082 > > http://files.pharo.org/image/60/60219.zip > >

Sept. 13, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60219 Home: https://github.com/pharo-project/pharo-core

Sept. 13, 2016