October 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1311: 22542 Tag and comment ManifestGTDebugger
by ci-pharo-ci-jenkins2＠inria.fr Oct. 6, 2018

Oct. 6, 2018

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

1 0

Re: [Pharo-dev] Slowness when loading code in Pharo 7?
by Alexandre Bergel Oct. 5, 2018

Oct. 5, 2018

Shouldnât the Metacello>>load be updated to disable EpMonitor? It seems to be an easy fix no? Alexandre > On Oct 2, 2018, at 11:31 PM, Juraj Kubelka via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Juraj Kubelka <juraj.kubelka(a)icloud.com> > Subject: Re: [Pharo-dev] Slowness when loading code in Pharo 7? > Date: October 2, 2018 at 11:31:59 PM GMT-3 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hi Martin, > > By disabling EpMonitor, the slowdown disappears. > > EpMonitor current disable. > [ Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > ] timeToRun "0:00:08:03.504â > > > Cheers, > Juraj > >> On Oct 2, 2018, at 18:14, Martin Dias <tinchodias(a)gmail.com> wrote: >> >> Hi Andrei. You can evaluate "EpMonitor current disable" before loading >> to compare times. >> El mar., 2 de oct. de 2018 a la(s) 11:18, Andrei Chis >> (chisvasileandrei(a)gmail.com) escribiÃ³: >>> >>> Hi, >>> >>> Are there any know slowdowns when loading code in Pharo 7? Usually on my machine (Mac - HighSierra) loading GToolkit in a Pharo 6.1 images takes around 9 minutes. In the latest Pharo 7 it takes 20 minutes. On two other newer laptops running Mac results are similar (15 minutes on Pharo 7 64it, and 7 minutes on Pharo 6.1 64bit). >>> >>> We have the impression that most of the times, the regression happens because of reading sources file. And the sources files are read because of checking Epicea method changes. We have not done a deep research on it, just whenever we do CMD+. it stops in that stage. >>> >>> Cheers, >>> Andrei >> > > > >

1 0

Re: [Pharo-dev] Slowness when loading code in Pharo 7?
by Peter Uhnak Oct. 5, 2018

Oct. 5, 2018

On Wed, Oct 3, 2018 at 7:31 PM Juraj Kubelka via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > Hi! > > I did the same measurement for Pharo 6.1. To summarize it I have those > results: > > By executing: > > -=-=-=- > EpMonitor current disable. > [ Metacello new > baseline: 'GToolkit'; > repository: 'github://feenkcom/gtoolkit/src'; > load. > ] timeToRun > -=-=-=- > > Pharo 6.1 64bit macOS: 6 minutes > Pharo 7.0 64bit macOS: 8 minutes > > With EpMonitor current enabled it is: > > Pharo 6.1 64bit macOS: 7 minutes > Pharo 7.0 64bit macOS: 15 minutes > So nice... I was just trying to install GToolkit in P6.1 on Windows (but with updated Iceberg)... it took over 1.5 hours (SmaCC was probably 30 minutes by itself), and then the image crashed... really looking forward to pre-made images :) Peter

3 2

Creating a new class using `Class new superclass:` blocks the image in Pharo 7
by Andrei Chis Oct. 5, 2018

Oct. 5, 2018

Hi, Executed in the latest Pharo 7 image (Pharo-7.0.0+alpha.build.1310.sha.a454977bb3d55bc4fcca3a57ac2fafcf137c0f30 (64 Bit)) the code below blocks the image (both with latest and stable vm on MacOs HighSierra). The vm does not crash but gets into a "Not Responding" state and does not get out: Class new superclass: GLMTransmission; setFormat: GLMTransmission format; classLayout: GLMTransmission classLayout copy; yourself Code like this is used in Moose in some tests and in SmaCC in the rewrite engine: Class new superclass: SmaCCRewriteMatchContext; setFormat: SmaCCRewriteMatchContext format; classLayout: SmaCCRewriteMatchContext classLayout copy; yourself. This worked in Pharo 6. Bug or here should be a different way to do this? Cheers, Andrei

2 4

[Pharo 7.0-dev] Build #1310: 22537 Tag ManifestMultilingualEncodings and related classes in Multilingual-Encodings-Manifest
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2018

Oct. 5, 2018

There is a new Pharo build available! The status of the build #1310 was: SUCCESS. The Pull Request #1875 was integrated: "22537 Tag ManifestMultilingualEncodings and related classes in Multilingual-Encodings-Manifest" Pull request url: https://github.com/pharo-project/pharo/pull/1875 Issue Url: https://pharo.fogbugz.com/f/cases/22537 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by monty Oct. 5, 2018

Oct. 5, 2018

2 1

[Pharo 7.0-dev] Build #1309: 22538 Tag ManifestFileSystemZip and related classes in FileSystem-Zip package
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2018

Oct. 5, 2018

There is a new Pharo build available! The status of the build #1309 was: FAILURE. The Pull Request #1876 was integrated: "22538 Tag ManifestFileSystemZip and related classes in FileSystem-Zip package" Pull request url: https://github.com/pharo-project/pharo/pull/1876 Issue Url: https://pharo.fogbugz.com/f/cases/22538 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1308: 22532-Adding-repository-to-package-via-MonticelloBrowser-is-broken
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2018

Oct. 5, 2018

There is a new Pharo build available! The status of the build #1308 was: FAILURE. The Pull Request #1870 was integrated: "22532-Adding-repository-to-package-via-MonticelloBrowser-is-broken" Pull request url: https://github.com/pharo-project/pharo/pull/1870 Issue Url: https://pharo.fogbugz.com/f/cases/22532 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1307: 22520-Deprecate-HistoryCollection
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2018

Oct. 5, 2018

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

1 0

[Pharo 7.0-dev] Build #1306: 22533-WelcomeHelp-should-not-have-hardcoded-version
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2018

Oct. 5, 2018

There is a new Pharo build available! The status of the build #1306 was: SUCCESS. The Pull Request #1868 was integrated: "22533-WelcomeHelp-should-not-have-hardcoded-version" Pull request url: https://github.com/pharo-project/pharo/pull/1868 Issue Url: https://pharo.fogbugz.com/f/cases/22533 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0