- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bad baseline practices

by Cyril Ferlicot

On Tue, Jan 15, 2019 at 6:03 PM Stephan Eggermont via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > > Iâm not sure why, but Iâve noticed baselines being changed to refer to > patch versions for releases. Why are the old configuration problems > repeated? Which project are you talking about? > > Stephan > > -- Cyril Ferlicot https://ferlicot.fr

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Esteban Lorenzano

Ok, it has to be me :) Esteban > On 15 Jan 2019, at 16:36, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hi, > I iouldn't reproduce in macos mojave. I downloaded with: > > curl https://get.pharo.org/64/70+vmLatest | bash > > And no problem with > > Stdio stdout << âOKâ > > Report: > > --- > Pharo7.0.0rc1 > Build information: > Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885 > (64 Bit) > Unnamed > > CoInterpreter VMMaker.oscog-eem.2504 uuid: > a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 > StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: > a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 > VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: > 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git > > Mac OS X built on Jan 5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible > Apple LLVM 7.3.0 (clang-703.0.31) > VMMaker versionString VM: 201901051900 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 > 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 > https://github.com/OpenSmalltalk/opensmalltalk-vm.git > CoInterpreter VMMaker.oscog-eem.2504 uuid: > a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 > StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: > a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 > --- > > MartÃn > > > El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano > (estebanlm(a)gmail.com) escribiÃ³: >> >> Thing is, it happens also with an older VM :( >> >> Esteban >> >>> On 15 Jan 2019, at 13:00, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Actually, I think it's rather a VM problem...? >>> >>> >>> On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: >>> >>>> Hello, >>>> >>>> Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). >>>> After doing >>>> >>>> Stdio stdout << âOKâ >>>> >>>> Iâm having this stack: >>>> >>>> File class(ProtoObject)>>primitiveFailed: >>>> File class(ProtoObject)>>primitiveFailed >>>> File class>>fileDescriptorType: >>>> File class>>fileDescriptorIsAvailable: >>>> Stdio class>>standardIOStreamNamed:forWrite: >>>> Stdio class>>stdout >>>> UndefinedObject>>DoIt >>>> OpalCompiler>>evaluate >>>> RubSmalltalkEditor>>evaluate:andDo: >>>> RubSmalltalkEditor>>highlightEvaluateAndDo: >>>> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint >>>> MorphicAlarm(MessageSend)>>value >>>> MorphicAlarm>>value: >>>> WorldState>>triggerAlarmsBefore: >>>> WorldState>>runLocalStepMethodsIn: >>>> WorldState>>runStepMethodsIn: >>>> WorldMorph>>runStepMethods >>>> WorldState>>doOneCycleNowFor: >>>> WorldState>>doOneCycleFor: >>>> WorldMorph>>doOneCycle >>>> WorldMorph class>>doOneCycle >>>> [ [ WorldMorph doOneCycle. >>>> Processor yield. >>>> false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... >>>> [ self value. >>>> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... >>>> >>>> Con someone confirm or refute this? >>>> >>>> Thanks! >>>> Esteban >>> >> >> >

Jan. 15, 2019

Bad baseline practices

by Stephan Eggermont

Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated? Stephan

Jan. 15, 2019

Re: [Pharo-dev] Managing of P7/P8

by Cyril Ferlicot

On Tue, Jan 15, 2019 at 4:38 PM Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > Hello, > as Pharo 8 development started I wonder: > > 1. When will it be possible to already get a Pharo 8 latest image > from ZeroConf. Because one requires ideally the latest image to contribute > - no? > I guess zeroconf for P8 will be set after Pharo 7 release. For now I get manually a Pharo 8 image from files.pharo.org and I use the Pharo 7 VM to contribute. > Or should one search/download from the CI server for the time being (which > would be cumbersome) > > 2. How will contributions still going to P7 handled regarding P8. > Typically a bugfix for P7 should also go into the P8 image - no? > But from the integration mails floating around I do not see > this is happening. > There is only few fixex that will still be integrated in P7 for the release. While the Pharo 7 development is still active there is often a merge of the P7 branch in the P8 branch to keep them up to date. After P7 I guess backported issues will be integrated in the P7 and P8 branches. > I would expect that a PR for Pharo 7 would also be merged into Pharo 8 branch. > If not the images could easily diverge too much or done fixes for P7 will not be in P8. > > Thanks in advance for clarification! > > Bye > T. > > -- Cyril Ferlicot https://ferlicot.fr

Jan. 15, 2019

Managing of P7/P8

by Torsten Bergmann

Hi, as Pharo 8 development started I wonder: 1. When will it be possible to already get a Pharo 8 latest image from ZeroConf. Because one requires ideally the latest image to contribute - no? Or should one search/download from the CI server for the time being (which would be cumbersome) 2. How will contributions still going to P7 handled regarding P8. Typically a bugfix for P7 should also go into the P8 image - no? But from the integration mails floating around I do not see this is happening. I would expect that a PR for Pharo 7 would also be merged into Pharo 8 branch. If not the images could easily diverge too much or done fixes for P7 will not be in P8. Thanks in advance for clarification! Bye T.

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Martin Dias

Hi, I iouldn't reproduce in macos mojave. I downloaded with: curl https://get.pharo.org/64/70+vmLatest | bash And no problem with Stdio stdout << âOKâ Report: --- Pharo7.0.0rc1 Build information: Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885 (64 Bit) Unnamed CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Mac OS X built on Jan 5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible Apple LLVM 7.3.0 (clang-703.0.31) VMMaker versionString VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 --- MartÃn El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano (estebanlm(a)gmail.com) escribiÃ³: > > Thing is, it happens also with an older VM :( > > Esteban > > > On 15 Jan 2019, at 13:00, Max Leske <maxleske(a)gmail.com> wrote: > > > > Actually, I think it's rather a VM problem...? > > > > > > On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > > > >> Hello, > >> > >> Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). > >> After doing > >> > >> Stdio stdout << âOKâ > >> > >> Iâm having this stack: > >> > >> File class(ProtoObject)>>primitiveFailed: > >> File class(ProtoObject)>>primitiveFailed > >> File class>>fileDescriptorType: > >> File class>>fileDescriptorIsAvailable: > >> Stdio class>>standardIOStreamNamed:forWrite: > >> Stdio class>>stdout > >> UndefinedObject>>DoIt > >> OpalCompiler>>evaluate > >> RubSmalltalkEditor>>evaluate:andDo: > >> RubSmalltalkEditor>>highlightEvaluateAndDo: > >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > >> MorphicAlarm(MessageSend)>>value > >> MorphicAlarm>>value: > >> WorldState>>triggerAlarmsBefore: > >> WorldState>>runLocalStepMethodsIn: > >> WorldState>>runStepMethodsIn: > >> WorldMorph>>runStepMethods > >> WorldState>>doOneCycleNowFor: > >> WorldState>>doOneCycleFor: > >> WorldMorph>>doOneCycle > >> WorldMorph class>>doOneCycle > >> [ [ WorldMorph doOneCycle. > >> Processor yield. > >> false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... > >> [ self value. > >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... > >> > >> Con someone confirm or refute this? > >> > >> Thanks! > >> Esteban > > > >

Jan. 15, 2019

[Pharo 7.0] Build #122: 22894-Unecessary-dialogs-during-refactorings

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #122 was: FAILURE. The Pull Request #2235 was integrated: "22894-Unecessary-dialogs-during-refactorings" Pull request url: https://github.com/pharo-project/pharo/pull/2235 Issue Url: https://pharo.fogbugz.com/f/cases/22894 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 15, 2019

[Pharo 8.0] Build #11: 2242-Sync-Pharo-7-and-8

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #11 was: SUCCESS. The Pull Request #2243 was integrated: "2242-Sync-Pharo-7-and-8" Pull request url: https://github.com/pharo-project/pharo/pull/2243 Issue Url: https://pharo.fogbugz.com/f/cases/2242 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Esteban Lorenzano

Thing is, it happens also with an older VM :( Esteban > On 15 Jan 2019, at 13:00, Max Leske <maxleske(a)gmail.com> wrote: > > Actually, I think it's rather a VM problem...? > > > On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > >> Hello, >> >> Iâm experiencing a problem with latest image (and latest vm) in Mac (Mojave). >> After doing >> >> Stdio stdout << âOKâ >> >> Iâm having this stack: >> >> File class(ProtoObject)>>primitiveFailed: >> File class(ProtoObject)>>primitiveFailed >> File class>>fileDescriptorType: >> File class>>fileDescriptorIsAvailable: >> Stdio class>>standardIOStreamNamed:forWrite: >> Stdio class>>stdout >> UndefinedObject>>DoIt >> OpalCompiler>>evaluate >> RubSmalltalkEditor>>evaluate:andDo: >> RubSmalltalkEditor>>highlightEvaluateAndDo: >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint >> MorphicAlarm(MessageSend)>>value >> MorphicAlarm>>value: >> WorldState>>triggerAlarmsBefore: >> WorldState>>runLocalStepMethodsIn: >> WorldState>>runStepMethodsIn: >> WorldMorph>>runStepMethods >> WorldState>>doOneCycleNowFor: >> WorldState>>doOneCycleFor: >> WorldMorph>>doOneCycle >> WorldMorph class>>doOneCycle >> [ [ WorldMorph doOneCycle. >> Processor yield. >> false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle.... >> [ self value. >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value.... >> >> Con someone confirm or refute this? >> >> Thanks! >> Esteban >

Jan. 15, 2019

Re: [Pharo-dev] A problem with latest image (64bit) ? (Please confirm)

by Max Leske

Actually, I think it's rather a VM problem...? On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote: > Hello, > > Iâm experiencing a problem with latest image (and latest vm) in Mac > (Mojave). > After doing > > Stdio stdout << âOKâ > > Iâm having this stack: > > File class(ProtoObject)>>primitiveFailed: > File class(ProtoObject)>>primitiveFailed > File class>>fileDescriptorType: > File class>>fileDescriptorIsAvailable: > Stdio class>>standardIOStreamNamed:forWrite: > Stdio class>>stdout > UndefinedObject>>DoIt > OpalCompiler>>evaluate > RubSmalltalkEditor>>evaluate:andDo: > RubSmalltalkEditor>>highlightEvaluateAndDo: > GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint > MorphicAlarm(MessageSend)>>value > MorphicAlarm>>value: > WorldState>>triggerAlarmsBefore: > WorldState>>runLocalStepMethodsIn: > WorldState>>runStepMethodsIn: > WorldMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > WorldMorph>>doOneCycle > WorldMorph class>>doOneCycle > [ [ WorldMorph doOneCycle. > Processor yield. > false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in > Block: [ [ WorldMorph doOneCycle.... > [ self value. > Processor terminateActive ] in BlockClosure>>newProcess in Block: [ > self value.... > > Con someone confirm or refute this? > > Thanks! > Esteban

Jan. 15, 2019