- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #206: Revert "Yield the CPU longer"
by ci-pharo-ci-jenkins2＠inria.fr Oct. 17, 2017

Oct. 17, 2017

There is a new Pharo build available! The status of the build #206 was: SUCCESS. The Pull Request #371 was integrated: "Revert "Yield the CPU longer"" Pull request url: https://github.com/pharo-project/pharo/pull/371 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #205: 20545-clean-announcers-in-sublcasses-of-Model
by ci-pharo-ci-jenkins2＠inria.fr Oct. 17, 2017

Oct. 17, 2017

There is a new Pharo build available! The status of the build #205 was: FAILURE. The Pull Request #367 was integrated: "20545-clean-announcers-in-sublcasses-of-Model" Pull request url: https://github.com/pharo-project/pharo/pull/367 Issue Url: https://pharo.fogbugz.com/f/cases/20545 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #204: Yield the CPU longer
by ci-pharo-ci-jenkins2＠inria.fr Oct. 17, 2017

Oct. 17, 2017

There is a new Pharo build available! The status of the build #204 was: FAILURE. The Pull Request #282 was integrated: "Yield the CPU longer" Pull request url: https://github.com/pharo-project/pharo/pull/282 Issue Url: https://pharo.fogbugz.com/f/cases/20425 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

VM specific mailing list
by Raffaello Giulietti Oct. 17, 2017

Oct. 17, 2017

Hi, is there a specific mailing list to discuss about Pharo's VM? Greetings Raffaello

2 1

[Pharo 7.0-dev] Build #203: 05723-Default-Working-Directory
by ci-pharo-ci-jenkins2＠inria.fr Oct. 16, 2017

Oct. 16, 2017

There is a new Pharo build available! The status of the build #203 was: SUCCESS. The Pull Request #92 was integrated: "05723-Default-Working-Directory" Pull request url: https://github.com/pharo-project/pharo/pull/92 Issue Url: https://pharo.fogbugz.com/f/cases/05723 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Test Runner: Walkback when storing result as progress reference
by Bernhard Pieber Oct. 16, 2017

Oct. 16, 2017

I just tripped over a walkback when clicking on the menu item âStore result as progress referenceâ in the Test Runner after having run all tests in a Pharo 6.1 (stable) image created by PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Has anyone seen this before? Cheers, Bernhard OpalEncoderForV3PlusClosures(Object)>>error: OpalEncoderForV3PlusClosures(OpalBytecodeEncoder)>>outOfRangeError:index:range:to: OpalEncoderForV3PlusClosures(OpalEncoderForV3)>>genPushLiteral: IRBytecodeGenerator>>pushLiteral: IRTranslatorV2>>visitPushLiteral: IRPushLiteral>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRTranslatorV2>>visitInstruction: [ :instr | self visitInstruction: instr ] in IRTranslatorV2(IRVisitor)>>visitSequence: in Block: [ :instr | self visitInstruction: instr ] OrderedCollection>>do: IRSequence>>do: IRTranslatorV2(IRVisitor)>>visitSequence: IRTranslatorV2>>visitSequence: IRSequence>>accept: IRTranslatorV2(IRVisitor)>>visitNode: [ :each | self visitNode: each ] in IRTranslatorV2(IRVisitor)>>visitNodes: in Block: [ :each | self visitNode: each ] SortedCollection(OrderedCollection)>>do: IRTranslatorV2(IRVisitor)>>visitNodes: IRTranslatorV2>>visitSequences: IRTranslatorV2>>visitMethod: IRMethod>>accept: IRTranslatorV2(IRVisitor)>>visitNode: IRMethod>>generate: IRMethod>>compiledMethodWith: RBMethodNode>>generate: [ [ ast := self parse. self doSemanticAnalysis. self callPlugins ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ [ ast := self parse.... BlockClosure>>on:do: OpalCompiler>>compile Metaclass(ClassDescription)>>compile:classified:withStamp:notifying:logSource: Metaclass(ClassDescription)>>compile:classified:withStamp:notifying:

2 1

Pharo 6.1 CompiledMethod(Object)>>doesNotUnderstand: #isMetaSide when running all tests
by Bernhard Pieber Oct. 16, 2017

Oct. 16, 2017

Dear Pharoers, I encountered a DNU when I ran all tests in a new Pharo 6.1 image created with PharoLauncher 1.0.1 on macOS Sierra 10.12.6. Should this work or is it a known issue? What is the Pharoâs policy concerning SUnit tests for stable releases? Cheers, Bernhard CompiledMethod(Object)>>doesNotUnderstand: #isMetaSide [ :rgMethod | | interestedClassName interestedClass | interestedClassName := anAnnouncement oldName. interestedClass := anAnnouncement classRenamed. rgMethod isMetaSide ifTrue: [ interestedClassName := interestedClassName , ' class'. interestedClass := interestedClass theMetaClass ]. rgMethod parentName = interestedClassName ifTrue: [ (interestedClass >> rgMethod selector) asFullRingDefinition ] ifFalse: [ rgMethod ] ] in MessageBrowser>>handleClassRenamed: in Block: [ :rgMethod | ... OrderedCollection>>collect: MessageBrowser>>handleClassRenamed: [ self handleClassRenamed: anAnnouncement ] in MessageBrowser>>classRenamed: in Block: [ self handleClassRenamed: anAnnouncement ] WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldMorph>>doOneCycleNow SystemProgressMorph>>refresh SystemProgressMorph>>update: MorphChanged>>deliverTo: SystemProgressMorph(Morph)>>handleUpdate: MessageSend>>value: MessageSend>>cull: MessageSend>>cull:cull: [ action cull: anAnnouncement cull: announcer ] in AnnouncementSubscription>>deliver: in Block: [ action cull: anAnnouncement cull: announcer ] BlockClosure>>on:do: BlockClosure>>on:fork: AnnouncementSubscription>>deliver: [ "Ensure delivery to remaining announcements" subscription deliver: anAnnouncement ] in SubscriptionRegistry>>deliver:to:startingAt: in Block: [ "Ensure delivery to remaining announcements" sub...etc... BlockClosure>>ifCurtailed: SubscriptionRegistry>>deliver:to:startingAt: SubscriptionRegistry>>deliver:to: SubscriptionRegistry>>deliver: Announcer>>announce: JobProgressMorph(Morph)>>doAnnounce: JobProgressMorph(Morph)>>changed: JobProgressMorph>>label: SystemProgressMorph class>>updateJob:

2 1

Esteban's ChangeLog week of 9 October 2017
by estebanlm＠gmail.com Oct. 16, 2017

Oct. 16, 2017

Hello! This is my weekly ChangeLog, from 9 October 2017 to 15 October 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=9/10/2017&to=15/10/2017 ChangeLog ========= 11 October 2017: ---------------- * I just integrated [case: 20492](https://pharo.fogbugz.com/f/cases/20492) (backport EPICEA changes) to Pharo6.1. This was seriously needed because the bugs were breaking some production code. 9 October 2017: --------------- * ... and after days of trying, I'm finally able to close [case: 18849](https://pharo.fogbugz.com/f/cases/18849) ! So we have an update Metacello in Pharo 7.0... and I can integrate Iceberg 0.6... tomorrow :) * I released a new version of [Iceberg (0.6.1)](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.1) This is just a bugfix release to allow install Iceberg 0.6 on Pharo 6.0. * And now I made [case: 20372](https://pharo.fogbugz.com/f/cases/20372) * Well, I started week by working a bit on Pharo 6.0 :) I just integrated [case: 20503](https://pharo.fogbugz.com/f/cases/20503) cheers! Esteban

1 0

PharoMinimal ?
by Sven Van Caekenberghe Oct. 14, 2017

Oct. 14, 2017

Hi, What is the story around PharoMinimal and related images ? Is there a writeup somewhere with instructions ? I see that we get **FANTASTIC** startup speed with it: $ cat /etc/issue Ubuntu 16.04.3 LTS $ ./pharo --version 5.0-201708271955 Sun Aug 27 20:09:20 UTC 2017 gcc 4.6.3 [Production Spur VM] CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Linux testing-gce-ebf45dd8-6a4c-43a5-abd0-e5d8673d05a4 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 i686 i686 i386 GNU/Linux plugin path: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955 [default: /home/audio359/pharo7/pharo-vm/lib/pharo/5.0-201708271955/] $ curl get.pharo.org/70-minimal | bash ... $ ./pharo Pharo.image printVersion [version] 'Pharo7.0' 'Pharo-7.0+alpha.build.172.sha.d13eed2f80fe19f29fd85ede8c4809d6a6986d4f (32 Bit)' $ time ./pharo Pharo.image eval '5 factorial' 120 real 0m0.083s user 0m0.034s sys 0m0.042s That is less than 1/10 of a second on a simple server ! Wow. Loading new code in that image seem hard though. I see that in http://files.pharo.org/image/70/ there are Pharomonticello & Pharometacello variants. Any pointers on usage/meaning ? Thx, Sven

8 20

[Pharo 7.0-dev] Build #201: 20529 Cleanup Kernel-Tests package regarding comments and categorization
by ci-pharo-ci-jenkins2＠inria.fr Oct. 14, 2017

Oct. 14, 2017

There is a new Pharo build available! The status of the build #201 was: SUCCESS. The Pull Request #352 was integrated: "20529 Cleanup Kernel-Tests package regarding comments and categorization" Pull request url: https://github.com/pharo-project/pharo/pull/352 Issue Url: https://pharo.fogbugz.com/f/cases/20529 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0