December 2017 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #363: 20825 Super setUp need to be called in Opal Compiler tests

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

There is a new Pharo build available! The status of the build #363 was: SUCCESS. The Pull Request #578 was integrated: "20825 Super setUp need to be called in Opal Compiler tests" Pull request url: https://github.com/pharo-project/pharo/pull/578 Issue Url: https://pharo.fogbugz.com/f/cases/20825 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

[Pharo 7.0-dev] Build #362: 20819 Fix variable assignment in RBScanner>>stripComment

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

There is a new Pharo build available! The status of the build #362 was: SUCCESS. The Pull Request #573 was integrated: "20819 Fix variable assignment in RBScanner>>stripComment" Pull request url: https://github.com/pharo-project/pharo/pull/573 Issue Url: https://pharo.fogbugz.com/f/cases/20819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Next OpenSmalltalkVM Release Planned For February 1

by Torsten Bergmann

see http://forum.world.st/ANN-Next-OpenSmalltalkVM-Release-Planned-For-February… What does it mean for Pharo-VM and release planning? Thx T.

Dec. 7, 2017

[Pharo 7.0-dev] Build #361: 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest

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

There is a new Pharo build available! The status of the build #361 was: SUCCESS. The Pull Request #580 was integrated: "20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest" Pull request url: https://github.com/pharo-project/pharo/pull/580 Issue Url: https://pharo.fogbugz.com/f/cases/20827 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 7, 2017

Re: [Pharo-dev] [TechTalk] Topics Wanted for 2018!

by Alexandre Bergel

Hi Marcus! Thanks for pushing the community! If there is a free slot at the end of January, I can do another tech talk on AI technique. I am thinking about a lecture on Genetic Algorithm and Genetic Programming. Let me know... Alexandre > On Dec 1, 2017, at 7:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > As you know, we are trying to have one Pharo tech-talk per month. > > The idea is to use this for > -> mini âLecturesâ > -> Demos of interesting Projects > -> Just some interesting topic to discuss with audio chat on Discord > > You can see the past topics here: > > http://pharo.org/TechTalk > > We will soon define the dates for the first half of 2018. If you want to do a techtalk > yourself (give a presentation / Demo or moderate a discussion), feel free to contact > me! You are able to pick a date that works best for you. > > > Marcus

Dec. 7, 2017

Running tests in MCMethodDefinitionTest

by Torsten Bergmann

Hi, a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) I noticed that from time to time you have trouble when running the test methods in this class one after the other several times. So sometimes it worked and sometimes not. I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which is used during the tests is unregistered and (when you run another test from this suite right afterwards) is not found anymore. Because in the test initialization it is not. This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown and one can easily run the tests several times independently. So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been the cause. The fix is part of PR https://github.com/pharo-project/pharo/pull/583 Bye T.

Dec. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Ben Coman

Perhaps PharoV60.sources got corrupted when downloaded. Try to replacing any you can find on your system... http://files.pharo.org/sources/PharoV60.sources.zip cheers -ben On 6 December 2017 at 14:55, Bernhard Pieber <bernhard(a)pieber.com> wrote: > Hi Sean, > > Thanks for taking the time to try to confirm this. Did you use Pharo > Launcher? I just tried it using get.pharo.org and donât see the > corruption. So it seems to be specific to Launcher somehow. :-/ > > Bernhard > > > Am 06.12.2017 um 01:04 schrieb Sean P. DeNigris <sean(a)clipperadams.com>: > > > > bpi wrote > >> Can anyone else confirm that? > > > > It seems okay for me: > > > > <http://forum.world.st/file/t128965/Screenshot_2017-12-05_19.jpeg> > > > > Image > > ----- > > Pharo6.0 > > Latest update: #60524 > > Unnamed > > > > Virtual Machine > > --------------- > > ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo > > CoInterpreter VMMaker.oscog-eem.2254 uuid: > > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > > VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 > > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > > > Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible > Apple > > LLVM 6.1.0 (clang-602.0.53) > > VMMaker versionString VM: 201707201942 > > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 > > 12:42:21 2017 -0700 $ Plugins: 201707201942 > > https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ > > CoInterpreter VMMaker.oscog-eem.2254 uuid: > > 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 > > StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: > > 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 > > > > Operating System/Hardware > > ------------------------- > > Mac OS 1013.1 intel > > > > > > > > ----- > > Cheers, > > Sean > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837. > html > > > > >

Dec. 6, 2017

Re: [Pharo-dev] Is Pharo spying on me?

by Peter UhnÃ¡k

On Wed, Dec 6, 2017 at 10:50 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > ShoreLIne is already removed from Pharo 7 > > -- Pavel > Good to know since I've just started using it. :)

Dec. 6, 2017

Re: [Pharo-dev] Corrupt method source in Pharo 6.1 (stable)

by Sean P. DeNigris

bpi wrote > Did you use Pharo Launcher? Yes ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 6, 2017

ANN: Pharo6.1 new release (I do not remember how this subject was)

by Esteban Lorenzano

So, I made a couple of changes: 20784 update Metacello since last update failed https://pharo.fogbugz.com/f/cases/20784 <https://pharo.fogbugz.com/f/cases/20784> and from a previous integration: 20176 Error in ByteArray>>booleanAt: https://pharo.fogbugz.com/f/cases/20176 <https://pharo.fogbugz.com/f/cases/20176> 20762 Pharo 6.1 has `pharo6.0.x` platform attribute instead of `pharo6.1.x` https://pharo.fogbugz.com/f/cases/20762 <https://pharo.fogbugz.com/f/cases/20762> 20103 Minor glitch in source code diff tool https://pharo.fogbugz.com/f/cases/20103 <https://pharo.fogbugz.com/f/cases/20103> So, the recent problems should be fixed. Now I can backport iceberg 0.6.4 :) cheers! Esteban

Dec. 6, 2017