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

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Stephane Ducasse

Hi Peter If you can go ahead please. I do not remember if I started to migrate PharoExtras/BitmapCharacterSet PharoExtras/OrderPreservingDictionary Now I suggested to Cyril to create a ston file that we archive with all the mappings that we need. So this way we will avoid that every body has to find all the bindings for jb jba jean-baptiste anrut jean-baptiste arnaud.... Stef On Wed, Oct 3, 2018 at 7:56 AM monty <monty2(a)programmer.net> wrote: > > That would be appreciated, if you can do it and preserve the history. > But you also need: > PharoExtras/BitmapCharacterSet > PharoExtras/OrderPreservingDictionary > > ___ > montyos.wordpress.com > > > Sent: Saturday, September 29, 2018 at 6:18 AM > From: "Peter Uhnak" <i.uhnak(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > Hi Stef, > > XMLParser is maintained by monty (I've CCed him). > > > Now the question still remains: who is planning to migrate the XML packages. > > I'd be happy to do that (including preserving the history), unless monty wants to do it themselves. > > Peter > > On Sat, Sep 29, 2018 at 10:39 AM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi >> >> I contacted the maintainer (but I'm not sure in fact who it is :) ) >> about the XML related packages in Pharo extras. >> >> XMLParser >> XMLParserHTML >> XMLParserStAX >> XMLSupport >> XMLWriter >> XPath >> >> I did not get any answer so may be I sent a mail to the wrong email address. >> Probably. >> Now the question still remains: who is planning to migrate the XML packages. >> I was planning to do it but I will not consider history because I do >> not know how to do it and I do not have the time to do it (sorry). And >> yes I work the weekends and this is bad and this is not even on Pharo. >> >> I was planning to spend some time on the baseline and making sure that >> we can load everything and run the tests. >> So let me know. >> >> Stef >>

Oct. 5, 2018

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Norbert Hartl

Great! And yet another reminder that all projects should consider moving to git. Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Oct. 5, 2018

[Pharo 7.0-dev] Build #1309: 22538 Tag ManifestFileSystemZip and related classes in FileSystem-Zip package

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

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…

Oct. 5, 2018

Re: [Pharo-dev] Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Gabriel Cotelli

+100 Thank you Sven. On Fri, Oct 5, 2018 at 9:06 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are > more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in > Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the > main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > >

Oct. 5, 2018

Conversion of my Libraries/Frameworks to GitHub/Tonel/TravisCI, Part 1

by Sven Van Caekenberghe

Hi, I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. So far I did the following: https://github.com/svenvc/NeoJSON https://github.com/svenvc/NeoCSV https://github.com/svenvc/ztimestamp https://github.com/svenvc/P3 https://github.com/svenvc/stamp https://github.com/svenvc/SimpleRedisClient https://github.com/svenvc/NeoConsole More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. After a while I will switch the Catalog entries and declare these repo the main ones. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

Oct. 5, 2018

[Pharo 7.0-dev] Build #1308: 22532-Adding-repository-to-package-via-MonticelloBrowser-is-broken

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

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…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1307: 22520-Deprecate-HistoryCollection

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

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…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1306: 22533-WelcomeHelp-should-not-have-hardcoded-version

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

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…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1305: 22500-LinkedListrejectthenCollect-is-slow

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

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

Oct. 5, 2018

[Pharo 7.0-dev] Build #1304: 22505-Storing-and-restoring-of-settings-cause-startup-errors

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

There is a new Pharo build available! The status of the build #1304 was: SUCCESS. The Pull Request #1867 was integrated: "22505-Storing-and-restoring-of-settings-cause-startup-errors" Pull request url: https://github.com/pharo-project/pharo/pull/1867 Issue Url: https://pharo.fogbugz.com/f/cases/22505 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 5, 2018

[Pharo 7.0-dev] Build #1303: 22437 Add a rule to check PackageManifest subclasses should be packaged with "Manifest" tag

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

There is a new Pharo build available! The status of the build #1303 was: SUCCESS. The Pull Request #1785 was integrated: "22437 Add a rule to check PackageManifest subclasses should be packaged with "Manifest" tag" Pull request url: https://github.com/pharo-project/pharo/pull/1785 Issue Url: https://pharo.fogbugz.com/f/cases/22437 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2018

[Pharo 7.0-dev] Build #1302: 22447 Cleanup ManifestSystemFileRegistry and related package

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

There is a new Pharo build available! The status of the build #1302 was: SUCCESS. The Pull Request #1795 was integrated: "22447 Cleanup ManifestSystemFileRegistry and related package" Pull request url: https://github.com/pharo-project/pharo/pull/1795 Issue Url: https://pharo.fogbugz.com/f/cases/22447 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2018

[Pharo 7.0-dev] Build #1301: 22461 Tag ManifestDeprecated70 and deprecated also ManifestDeprecated70

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

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

Oct. 4, 2018

[Pharo 7.0-dev] Build #1300: 22255-Either-Pragma-should-compare-methodSelector-or-PragmaCollector-should-account-for-bad-comparison

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

There is a new Pharo build available! The status of the build #1300 was: SUCCESS. The Pull Request #1745 was integrated: "22255-Either-Pragma-should-compare-methodSelector-or-PragmaCollector-should-account-for-bad-comparison" Pull request url: https://github.com/pharo-project/pharo/pull/1745 Issue Url: https://pharo.fogbugz.com/f/cases/22255 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2018

[Pharo 7.0-dev] Build #1299: Committing changes from GustavoSantos/Refactoring2 on Smalltalkhub

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

There is a new Pharo build available! The status of the build #1299 was: SUCCESS. The Pull Request #1695 was integrated: "Committing changes from GustavoSantos/Refactoring2 on Smalltalkhub" Pull request url: https://github.com/pharo-project/pharo/pull/1695 Issue Url: https://pharo.fogbugz.com/f/cases/22337 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2018

[Pharo 7.0-dev] Build #1298: Fix for issue 22516

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

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

Oct. 4, 2018

[Pharo 7.0-dev] Build #1297: Revert "22284-Freeze-during-startup"

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

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

Oct. 4, 2018

[Pharo 7.0-dev] Build #1296: 22526 Tag ManifestMorphicWidgetsPluggable and related classes

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

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

Oct. 4, 2018

[Pharo 7.0-dev] Build #1295: 22525 Tag and comment ManifestReflectivity to have a proper Reflectivity package

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

There is a new Pharo build available! The status of the build #1295 was: SUCCESS. The Pull Request #1862 was integrated: "22525 Tag and comment ManifestReflectivity to have a proper Reflectivity package" Pull request url: https://github.com/pharo-project/pharo/pull/1862 Issue Url: https://pharo.fogbugz.com/f/cases/22525 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 4, 2018

Re: [Pharo-dev] :: Separator in class names

by phil＠highoctane.be

I'd like to have it. At least for my own packages... Phil On Thu, Oct 4, 2018 at 9:52 AM Torsten Bergmann <astares(a)gmx.de> wrote: > Again several years passed by and we still have no solution for Namespaces. > > At least I would like to have support for a separator. Details are in this > thread from 2016 (!): > > http://forum.world.st/Separator-in-class-names-td4926162.html > > I still ask if this is something we can get on board for P7 or P8? > > Thx > T. > > >

Oct. 4, 2018

:: Separator in class names

by Torsten Bergmann

Again several years passed by and we still have no solution for Namespaces. At least I would like to have support for a separator. Details are in this thread from 2016 (!): http://forum.world.st/Separator-in-class-names-td4926162.html I still ask if this is something we can get on board for P7 or P8? Thx T.

Oct. 4, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by tinchodias＠gmail.com

On Wed, 2018-10-03 at 20:08 +0200, Peter Uhnak wrote: > > > On Wed, Oct 3, 2018 at 7:31 PM Juraj Kubelka via Pharo-dev <pharo-dev > @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 I ran the attached script on my debian 64 bits (disk: slow HDD w/ext4, cpu: i5 ram: 12gb). Here, the slowdown from 61 to 70 is not as evident as in your cases.Â It's only me? It can help if others can run the script and report your results in other computers and OSs. Two output examples: --- pharo 61 * disabled: 0:00:07:30.783 * enabled: 0:00:08:27.931 pharo 70 * disabled: 0:00:08:24.403 * enabled: 0:00:09:12.858 --- pharo 61 * disabled: 0:00:08:16.036 * enabled: 0:00:09:21.368 pharo 70 * disabled: 0:00:08:06.57 * enabled: 0:00:10:05.194 --- pharo 61 * disabled: 0:00:07:39.538 * enabled: 0:00:08:33.778 pharo 70 * disabled: 0:00:07:23.528 * enabled: 0:00:09:11.453 --- Note: the script removes pharo-local/ before loading the code to download again everything (and I don't have configured a central repo in personal settings or something like that). It should be more fair to compare to have locallyÂ cached as much as possible. I tried once and it was reducing a couple of minutes, but the conclusion was the same. Additionally: In both 61 and 70, I browsed the resulting ombu file (>110 mb), it was not thaat bad... ~5 seconds when I clicked on the file, and then almost no delay on scroll and when clicking on a particular change. But: The problem was when I clicked on a filter and it started to parse each change... I waited like 10 minutes and then closed it. No visual feedback, and looks too inefficient. MartÃn

Oct. 4, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by Peter Uhnak

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

Oct. 3, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by tinchodias＠gmail.com

On Tue, 2018-10-02 at 23:31 -0300, Juraj Kubelka via Pharo-dev wrote: > I can profile it to see if there is something wrong, or it's just that a lot of source code from GT and dependencies is written to disk and then the only thing can do is disable change recording (and maybe then re-enabling it after load). (but I have linux)

Oct. 3, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by Juraj Kubelka

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 Cheers, Juraj > On Oct 2, 2018, at 23:31, 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 23:31:59 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 >> > > > >

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Sven Van Caekenberghe

> On 3 Oct 2018, at 15:04, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 3 Oct 2018, at 14:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Metacello new >> repository: 'github://svenvc/ztimestamp'; >> baseline: 'ZTimestamp'; >> load. > > This part is bad. > You need: > > Metacello new > repository: 'github://svenvc/ztimestamp/repository'; > baseline: 'ZTimestamp'; > load. > > (You miss to point to the repository). Ah, I did not see that, I understand, now it works: Fetched -> BaselineOfZTimestamp-tonel.1 --- github://svenvc/ztimestamp:master/repository --- github://svenvc/ztimestamp:master/repository Loaded -> BaselineOfZTimestamp-tonel.1 --- github://svenvc/ztimestamp:master/repository --- github://svenvc/ztimestamp:master/repository Loading baseline of BaselineOfZTimestamp... Fetched -> ZTimestamp-tonel.1 --- github://svenvc/ztimestamp:master/repository --- github://svenvc/ztimestamp:master/repository Loaded -> ZTimestamp-tonel.1 --- github://svenvc/ztimestamp:master/repository --- cache ...finished baseline > And btw, there is an error here: > > https://github.com/svenvc/ztimestamp/blob/master/repository/.properties > > (File is malformed. It will not affect the loading, but you may want to fix it). OK, fixed it, thanks for your help. > Esteban >

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Esteban Lorenzano

> On 3 Oct 2018, at 14:26, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Metacello new > repository: 'github://svenvc/ztimestamp <github://svenvc/ztimestamp>'; > baseline: 'ZTimestamp'; > load. This part is bad. You need: Metacello new repository: 'github://svenvc/ztimestamp/repository'; baseline: 'ZTimestamp'; load. (You miss to point to the repository). And btw, there is an error here: https://github.com/svenvc/ztimestamp/blob/master/repository/.properties <https://github.com/svenvc/ztimestamp/blob/master/repository/.properties> (File is malformed. It will not affect the loading, but you may want to fix it). Esteban

Oct. 3, 2018

[Pharo 7.0-dev] Build #1294: 22515 Package ManifestGraphicsDisplayObjects and related classes in Graphics-Display Objects

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

There is a new Pharo build available! The status of the build #1294 was: FAILURE. The Pull Request #1855 was integrated: "22515 Package ManifestGraphicsDisplayObjects and related classes in Graphics-Display Objects" Pull request url: https://github.com/pharo-project/pharo/pull/1855 Issue Url: https://pharo.fogbugz.com/f/cases/22515 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Sven Van Caekenberghe

Well, I tried but no luck: Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:pharo-6.1_dev/repository'; onConflict: [ :ex | ex useIncoming ]; load. Metacello new repository: 'github://pharo-vcs/tonel'; baseline: 'Tonel'; load. Metacello new repository: 'github://svenvc/ztimestamp'; baseline: 'ZTimestamp'; load. Fetched -> BaselineOfMetacello-EstebanLorenzano.104 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Loaded -> BaselineOfMetacello-EstebanLorenzano.104 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Loading baseline of BaselineOfMetacello... Fetched -> Metacello-Base-EstebanLorenzano.125 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Core-EstebanLorenzano.840 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-MC-EstebanLorenzano.737 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-PharoCommonPlatform-EstebanLorenzano.22 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-ToolBox-EstebanLorenzano.150 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Cypress-CyrilFerlicot.8 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Platform.pharo60-EstebanLorenzano.1508155584 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-FileTree-EstebanLorenzano.39 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-GitBasedRepository-EstebanLorenzano.25 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Bitbucket-EstebanLorenzano.7 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-GitHub-EstebanLorenzano.47 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Reference-dkh.36 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-Tutorial-dkh.26 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsMCResources-EstebanLorenzano.35 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsCommonMC.pharo20-dkh.5 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsMCCore-EstebanLorenzano.10 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsMC-EstebanLorenzano.410 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsReference-dkh.20 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Fetched -> Metacello-TestsPlatform.squeakCommon-EstebanLorenzano.23 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- github://metacello/metacello:pharo-6.1_dev/repository Loaded -> Metacello-Base-EstebanLorenzano.125 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-Core-EstebanLorenzano.840 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-MC-EstebanLorenzano.737 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-PharoCommonPlatform-EstebanLorenzano.22 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-ToolBox-EstebanLorenzano.150 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-Cypress-CyrilFerlicot.8 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-Platform.pharo60-EstebanLorenzano.1508155584 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache Loaded -> Metacello-FileTree-EstebanLorenzano.39 --- github://metacello/metacello:pharo-6.1_dev/repository [382ac2b:pharo-6.1_dev] --- cache MCGitBasedNetworkRepository>>initialize (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>directory (directory is Undeclared) MCGitBasedNetworkRepository>>flushForScriptGet (directory is Undeclared) MCGitBasedNetworkRepository>>flushCache (directory is Undeclared) Loaded -> Metacello-GitBasedRepository-EstebanLorenzano.25 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-Bitbucket-EstebanLorenzano.7 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-GitHub-EstebanLorenzano.47 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-Reference-dkh.36 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-Tutorial-dkh.26 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-TestsMCResources-EstebanLorenzano.35 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Evaluated -> Metacello-TestsMCResources >> testResourcePostLoadDoIt Loaded -> Metacello-TestsCommonMC.pharo20-dkh.5 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-TestsMCCore-EstebanLorenzano.10 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-TestsMC-EstebanLorenzano.410 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-TestsReference-dkh.20 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Loaded -> Metacello-TestsPlatform.squeakCommon-EstebanLorenzano.23 --- github://metacello/metacello:pharo-6.1_dev/repository --- cache Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197 ...finished baseline Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master --- github://pharo-vcs/tonel:master Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master --- github://pharo-vcs/tonel:master Loading baseline of BaselineOfTonel... Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master --- github://pharo-vcs/tonel:master Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master --- cache Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master --- cache Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master --- cache ...finished baseline ...RETRY->BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...FAILED->BaselineOfZTimestamp > On 3 Oct 2018, at 14:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi Sven, > > You still need latest metacello. > This is the list of requirements to use metacello and tonel. > > 1. Latest metacello: > > Metacello new > baseline: 'Metacello'; > repository: 'github://metacello/metacello:pharo-6.1_dev/repository'; > onConflict: [ :ex | ex useIncoming ]; > load. > > 2. Tonel > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Both can be loaded in any order, but you need both :) > > Esteban > >> On 3 Oct 2018, at 14:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. >> >> I got a fresh 6.0 and I installed Tonel into it using >> >> Metacello new >> repository: 'github://pharo-vcs/tonel'; >> baseline: 'Tonel'; >> load. >> >> Which went OK >> >> Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loading baseline of BaselineOfTonel... >> Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> ...finished baseline >> >> Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info >> >> Metacello new >> repository: 'github://svenvc/ztimestamp'; >> baseline: 'ZTimestamp'; >> load. >> >> This fails >> >> ...RETRY->BaselineOfZTimestamp >> ...RETRY->BaselineOfZTimestamp >> ...FAILED->BaselineOfZTimestamp >> >> Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master >> >> What am I doing wrong here ? >> >> Thx, >> >> Sven >> >> > >

Oct. 3, 2018

[Pharo 7.0-dev] Build #1293: 22163-Memory-Leak-GLMHintableActionButtonBrick

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

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

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Esteban Lorenzano

> On 3 Oct 2018, at 14:12, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. >> >> I got a fresh 6.0 and I installed Tonel into it using >> >> Metacello new >> repository: 'github://pharo-vcs/tonel'; >> baseline: 'Tonel'; >> load. >> >> Which went OK >> >> Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loading baseline of BaselineOfTonel... >> Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master >> Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache >> ...finished baseline >> >> Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info >> >> Metacello new >> repository: 'github://svenvc/ztimestamp'; >> baseline: 'ZTimestamp'; >> load. >> >> This fails >> >> ...RETRY->BaselineOfZTimestamp >> ...RETRY->BaselineOfZTimestamp >> ...FAILED->BaselineOfZTimestamp >> >> Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master >> >> What am I doing wrong here ? >> > That is the behaviour I was talking about. Tonel in my case had read problem at the end of the stream. But I couldnât figure out what it is This is not Tonel. This is Metacello that still does not knows how to handle tonel (thatâs why you need latest version) Esteban > > Norbert >> Thx, >> >> Sven

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Esteban Lorenzano

Hi Sven, You still need latest metacello. This is the list of requirements to use metacello and tonel. 1. Latest metacello: Metacello new baseline: 'Metacello'; repository: 'github://metacello/metacello:pharo-6.1_dev/repository'; onConflict: [ :ex | ex useIncoming ]; load. 2. Tonel Metacello new repository: 'github://pharo-vcs/tonel'; baseline: 'Tonel'; load. Both can be loaded in any order, but you need both :) Esteban > On 3 Oct 2018, at 14:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. > > I got a fresh 6.0 and I installed Tonel into it using > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Which went OK > > Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loading baseline of BaselineOfTonel... > Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > ...finished baseline > > Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info > > Metacello new > repository: 'github://svenvc/ztimestamp'; > baseline: 'ZTimestamp'; > load. > > This fails > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestamp > > Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master > > What am I doing wrong here ? > > Thx, > > Sven > >

Oct. 3, 2018

Re: [Pharo-dev] Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Norbert Hartl

> Am 03.10.2018 um 14:02 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. > > I got a fresh 6.0 and I installed Tonel into it using > > Metacello new > repository: 'github://pharo-vcs/tonel'; > baseline: 'Tonel'; > load. > > Which went OK > > Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loading baseline of BaselineOfTonel... > Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master > Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache > ...finished baseline > > Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info > > Metacello new > repository: 'github://svenvc/ztimestamp'; > baseline: 'ZTimestamp'; > load. > > This fails > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestamp > > Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master > > What am I doing wrong here ? > That is the behaviour I was talking about. Tonel in my case had read problem at the end of the stream. But I couldnât figure out what it is Norbert > Thx, > > Sven > >

Oct. 3, 2018

Loading GitHub/Tonel/BaselineOf code in Pharo 6.0

by Sven Van Caekenberghe

So I am trying to load GitHub/Tonel/BaselineOf code in Pharo 6.0. I got a fresh 6.0 and I installed Tonel into it using Metacello new repository: 'github://pharo-vcs/tonel'; baseline: 'Tonel'; load. Which went OK Fetched -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loaded -> BaselineOfTonel-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loading baseline of BaselineOfTonel... Fetched -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Fetched -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- github://pharo-vcs/tonel:master Loaded -> MonticelloTonel-Core-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache Loaded -> MonticelloTonel-FileSystem-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache Loaded -> MonticelloTonel-Tests-cypress.1 --- github://pharo-vcs/tonel:master [0317649:master] --- cache ...finished baseline Then I try to load some code from me that has been converted to GitHub/Tonel/BaselineOf and that works fine in 6.1/7.0 and contains all meta info Metacello new repository: 'github://svenvc/ztimestamp'; baseline: 'ZTimestamp'; load. This fails ...RETRY->BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...FAILED->BaselineOfZTimestamp Could not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /Users/sven/Tmp/pharo6/pharo-local/package-cache github://svenvc/ztimestamp:master What am I doing wrong here ? Thx, Sven

Oct. 3, 2018

[Pharo 7.0-dev] Build #1292: 22094-Scrollbars-need-to-take-displayScaleFactor-into-account

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

There is a new Pharo build available! The status of the build #1292 was: FAILURE. The Pull Request #1852 was integrated: "22094-Scrollbars-need-to-take-displayScaleFactor-into-account" Pull request url: https://github.com/pharo-project/pharo/pull/1852 Issue Url: https://pharo.fogbugz.com/f/cases/22094 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

[Pharo 7.0-dev] Build #1291: 22513-Update-ProfStef-and-fix-spelling-mistakes

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

There is a new Pharo build available! The status of the build #1291 was: SUCCESS. The Pull Request #1853 was integrated: "22513-Update-ProfStef-and-fix-spelling-mistakes" Pull request url: https://github.com/pharo-project/pharo/pull/1853 Issue Url: https://pharo.fogbugz.com/f/cases/development Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 3, 2018

Re: [Pharo-dev] [ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]

by Guillermo Polito

Yes +1 on the thanks! Also it's great to read your emails to learn new stuff :) On Tue, Oct 2, 2018 at 8:30 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ben I would like to thank you! > Simply. > > Stef > On Tue, Oct 2, 2018 at 5:58 AM Ben Coman <btc(a)openinworld.com> wrote: > > > > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> > >> Do we really need 8 delay schedulers (DelayMicrosecondScheduler, > DelayMillisecondScheduler, DelayNullScheduler, > DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, > DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) ? > > > > > > I've cleaned the delay scheduling subsystem [1] to condense these > alternatives and separate orthogonal functionality. After a couple of > reviews this was integrated and made active in last week's Build 1273. > Could anyone with test scenarios from previous issues with delays have a > bash at stressing the latest build. > > > > The old(existing) DelaySpinScheduler remains in the system so it can be > activated as a point of comparison (System > Settings > System > Delay > Scheduler). Pending any adverse reports the final step will be to remove > the old hierarchy next week. > > > > There remain separate mutex and semaphore based schedulers since: > > * they differ by only a couple of overridden methods > > * their slightly different implementations help highlight the core > algorithm > > * they provide a simple in-Image example of different synchronisation > mechanisms. > > * in isolating edge cases its useful to be able to compare results > between implementations > > > > I've retained both microsecond and millisecond operation, > > but extracted into "ticker" classes orthogonal to the "scheduling" > classes since: > > * it makes the core scheduling algorithm independent of time base > > * millisecond (or other custom) timebase might(?) be more efficient on > smaller 32-bit embedded systems > > * tests can now simulate ticker time to avoid tests interfering with > system's-active-scheduler VM interaction (which may be the source of some > random CI failures) > > * delay scheduler tests are now independent of real-time (which may be > the source of some random CI failures where delays are affected by varying > CI server loads) > > * when multi-threaded FFI callbacks become available, may facilitate > experimenting with: > > * wake-up from native timers > > * wake-up of embedded Pharo from the encompassing system > > > > > > Other refactors: > > * during system snapshot, save/restore of resumption times was happening > at user priority which risks a race condition reported at [2]. *All* > modification of resumption times now occurs at timing/highest priority. > > > > > > [1] > https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… > > [2] https://pharo.manuscript.com/f/cases/18359/ > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 3, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Marcus Denker

Ok, so the upgrade of the server contract did not help. There is a CDN included, I will try to enable that next (but CDNs cache by name, so we need to make sure we invalidate the cacheâ¦) I will do a calculation what S3 would cost, too. Marcus > On 3 Oct 2018, at 00:59, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > I'm reviving this because I can't finish the download of an image using the latest Pharo launcher. > > I'm timeout errors when attempting to download it. Tried 5 times at different intervals. > > > <image.png> > > Any idea of what could be happening? > > Esteban A. Maringolo > > > El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (<emaringolo(a)gmail.com <mailto:emaringolo@gmail.com>>) escribiÃ³: > Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? > > Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. > > This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. > > <node-pharo.png> > > The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. > > Regards, > > Esteban A. Maringolo > > ps: When I finished writing this email, this was the progress... > <image.png>

Oct. 3, 2018

[Pharo 7.0-dev] Build #1290: 22511-TestValueWithinFix-is-failing-randomly

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

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

Oct. 3, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by monty

It would also prefer an SS3-based STHub, at least as an alternative to GitHub. ___ montyos.wordpress.com > Sent: Saturday, September 29, 2018 at 6:43 AM > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > Hi Sven > > SmalltalkHub is dying. And we will turn it readonly by January. > Esteban has something else to do that to take care of it. It is a legacy. > We are about to announce that we cannot create account and projects anymore. > We are waiting to do that after the mooc. > Now you want to use Squeaksource or SS3 I do not want. > I want to use github and I guess that I do not have to explain why for real. > > Stef > > On Sat, Sep 29, 2018 at 11:27 AM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > I think that would be monty, email addresses (CC-ed) > > > > monty2(a)programmer.net > > > > I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... > > > > What does not work for you ? > > > > Sven > > > > > On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > > > Hi > > > > > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > > > about the XML related packages in Pharo extras. > > > > > > XMLParser > > > XMLParserHTML > > > XMLParserStAX > > > XMLSupport > > > XMLWriter > > > XPath > > > > > > I did not get any answer so may be I sent a mail to the wrong email address. > > > Probably. > > > Now the question still remains: who is planning to migrate the XML packages. > > > I was planning to do it but I will not consider history because I do > > > not know how to do it and I do not have the time to do it (sorry). And > > > yes I work the weekends and this is bad and this is not even on Pharo. > > > > > > I was planning to spend some time on the baseline and making sure that > > > we can load everything and run the tests. > > > So let me know. > > > > > > Stef > > > > > > > > >

Oct. 3, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by monty

Oct. 3, 2018

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by monty

Again, for the record, I have no idea who "monty kamath" (monthkamath@gmailcom) is. Do not send any inquiries to him about those projects. I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. ___ montyos.wordpress.com > Sent: Saturday, September 29, 2018 at 5:26 AM > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Cc: monty <monty2(a)programmer.net>, montykamath(a)gmail.com > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > I think that would be monty, email addresses (CC-ed) > > monty2(a)programmer.net > montykamath(a)gmail.com > > I should note that he has been very good at maintaining the XML packages (the specs of which are super complex), and as far as I know, the code works under Pharo 7 ... > > What does not work for you ? > > Sven > > > On 29 Sep 2018, at 10:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > Hi > > > > I contacted the maintainer (but I'm not sure in fact who it is :) ) > > about the XML related packages in Pharo extras. > > > > XMLParser > > XMLParserHTML > > XMLParserStAX > > XMLSupport > > XMLWriter > > XPath > > > > I did not get any answer so may be I sent a mail to the wrong email address. > > Probably. > > Now the question still remains: who is planning to migrate the XML packages. > > I was planning to do it but I will not consider history because I do > > not know how to do it and I do not have the time to do it (sorry). And > > yes I work the weekends and this is bad and this is not even on Pharo. > > > > I was planning to spend some time on the baseline and making sure that > > we can load everything and run the tests. > > So let me know. > > > > Stef > > > >

Oct. 3, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by Juraj Kubelka

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 >

Oct. 3, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Esteban Maringolo

Now I sent the mail it completed. :-) Esteban A. Maringolo El mar., 2 oct. 2018 a las 19:59, Esteban Maringolo (<emaringolo(a)gmail.com>) escribiÃ³: > I'm reviving this because I can't finish the download of an image using > the latest Pharo launcher. > > I'm timeout errors when attempting to download it. Tried 5 times at > different intervals. > > > [image: image.png] > > Any idea of what could be happening? > > Esteban A. Maringolo > > > El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (< > emaringolo(a)gmail.com>) escribiÃ³: > >> Is there a reason why the latest version of the builds linked from the >> website are not hosted in some CDN, Amazon S3 or similar? >> >> Maybe in Europe the speed is fast, but where I am (Argentina) it is >> really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks >> of 40KB/s. >> >> This is an pitiful boarding experience, that will make many cancel it >> even before getting to open the downloaded launcher. >> >> [image: node-pharo.png] >> >> The screenshot shows that is not a problem with my home connection, which >> isn't the fastest but is "normal" for my use cases. >> >> Regards, >> >> Esteban A. Maringolo >> >> ps: When I finished writing this email, this was the progress... >> [image: image.png] >> >

Oct. 2, 2018

Re: [Pharo-dev] Pharo Downloads are sluggish

by Esteban Maringolo

I'm reviving this because I can't finish the download of an image using the latest Pharo launcher. I'm timeout errors when attempting to download it. Tried 5 times at different intervals. [image: image.png] Any idea of what could be happening? Esteban A. Maringolo El mar., 18 sept. 2018 a las 21:03, Esteban Maringolo (<emaringolo(a)gmail.com>) escribiÃ³: > Is there a reason why the latest version of the builds linked from the > website are not hosted in some CDN, Amazon S3 or similar? > > Maybe in Europe the speed is fast, but where I am (Argentina) it is really > slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of > 40KB/s. > > This is an pitiful boarding experience, that will make many cancel it even > before getting to open the downloaded launcher. > > [image: node-pharo.png] > > The screenshot shows that is not a problem with my home connection, which > isn't the fastest but is "normal" for my use cases. > > Regards, > > Esteban A. Maringolo > > ps: When I finished writing this email, this was the progress... > [image: image.png] >

Oct. 2, 2018

Re: [Pharo-dev] Slowness when loading code in Pharo 7?

by Martin Dias

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

Oct. 2, 2018

Re: [Pharo-dev] [ANN] 22477 DelayScheduler cleanup and refactoring [was: Where do we go now ?]

by Stephane Ducasse

Ben I would like to thank you! Simply. Stef On Tue, Oct 2, 2018 at 5:58 AM Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, 13 Apr 2018 at 13:56, Benoit St-Jean via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> Do we really need 8 delay schedulers (DelayMicrosecondScheduler, DelayMillisecondScheduler, DelayNullScheduler, DelayExperimentalSpinScheduler, DelaySpinScheduler, DelayTicklessScheduler, DelayExperimentalCourageousScheduler, DelayExperimentalSemaphoreScheduler) ? > > > I've cleaned the delay scheduling subsystem [1] to condense these alternatives and separate orthogonal functionality. After a couple of reviews this was integrated and made active in last week's Build 1273. Could anyone with test scenarios from previous issues with delays have a bash at stressing the latest build. > > The old(existing) DelaySpinScheduler remains in the system so it can be activated as a point of comparison (System > Settings > System > Delay Scheduler). Pending any adverse reports the final step will be to remove the old hierarchy next week. > > There remain separate mutex and semaphore based schedulers since: > * they differ by only a couple of overridden methods > * their slightly different implementations help highlight the core algorithm > * they provide a simple in-Image example of different synchronisation mechanisms. > * in isolating edge cases its useful to be able to compare results between implementations > > I've retained both microsecond and millisecond operation, > but extracted into "ticker" classes orthogonal to the "scheduling" classes since: > * it makes the core scheduling algorithm independent of time base > * millisecond (or other custom) timebase might(?) be more efficient on smaller 32-bit embedded systems > * tests can now simulate ticker time to avoid tests interfering with system's-active-scheduler VM interaction (which may be the source of some random CI failures) > * delay scheduler tests are now independent of real-time (which may be the source of some random CI failures where delays are affected by varying CI server loads) > * when multi-threaded FFI callbacks become available, may facilitate experimenting with: > * wake-up from native timers > * wake-up of embedded Pharo from the encompassing system > > > Other refactors: > * during system snapshot, save/restore of resumption times was happening at user priority which risks a race condition reported at [2]. *All* modification of resumption times now occurs at timing/highest priority. > > > [1] https://pharo.manuscript.com/f/cases/22477/DelayScheduler-cleanup-and-refac… > [2] https://pharo.manuscript.com/f/cases/18359/

Oct. 2, 2018

Re: [Pharo-dev] Tonel support for Travis CI smalltalkCI for Pharo < 6.1

by Esteban Lorenzano

Btw tonel may be installed in a preLoad, when needed. > On 2 Oct 2018, at 17:43, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > useLatestMetacello will not load Tonel, it will use it if it finds it. > Something we may correct, if needed. > >> On 2 Oct 2018, at 17:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >> >>> On 2 Oct 2018, at 17:11, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> >>>> If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? >>> >>> Tonel is not in <P6.1. You can try to add >>> >>> #useLatestMetacello : true, >>> >>> to your smalltalkci.ston file, but I believe smalltalkCI actually uses iceberg to load tonel projects... which would be much harder to backport. >>> >>> But try with #useLatestMetacello and let us know. >> >> Thanks for your reply. >> >> That does not seem to work (same result for 6.0 and 5.0, ), >> >> ...RETRY->BaselineOfZTimestamp >> ...RETRY->BaselineOfZTimestamp >> ...FAILED->BaselineOfZTimestamp[31mCould not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /home/travis/smalltalkCI-master/_builds/package-cache filetree:///home/travis/build/svenvc/ztimestamp/repository >> MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: >> >> and extra failures for 7.0 ! >> >> Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] >> Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] >> Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] >> Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] >> Loading baseline of BaselineOfMetacello...MetacelloNameNotDefinedError: project group, or package named: 'FileTree' not found when used in requires: or includes: field of package: 'Metacello-FileTree' for version: baseline of BaselineOfMetacello. >> MetacelloNameNotDefinedError >> >> >>> Peter >>> >>> On Tue, Oct 2, 2018 at 4:53 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> Hi, >>> >>> I managed to get successful BaselineOf builds out of a GitHub in Tonel format for Pharo 7 (64 & 32 bits) and Pharo 6.1 using Travis CI and smalltalkCI. >>> >>> However, this does not seem to work for Pharo 6 or 5. Is this to be expected ? >>> >>> You can see a build failure here: >>> >>> https://travis-ci.org/svenvc/ztimestamp/builds/436146649 >>> >>> If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? This is of course related to my previous question about the reach of Tonel/github. >>> >>> Thx, >>> >>> Sven >> >> >

Oct. 2, 2018

Re: [Pharo-dev] Tonel support for Travis CI smalltalkCI for Pharo < 6.1

by Esteban Lorenzano

useLatestMetacello will not load Tonel, it will use it if it finds it. Something we may correct, if needed. > On 2 Oct 2018, at 17:37, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 2 Oct 2018, at 17:11, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >>> If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? >> >> Tonel is not in <P6.1. You can try to add >> >> #useLatestMetacello : true, >> >> to your smalltalkci.ston file, but I believe smalltalkCI actually uses iceberg to load tonel projects... which would be much harder to backport. >> >> But try with #useLatestMetacello and let us know. > > Thanks for your reply. > > That does not seem to work (same result for 6.0 and 5.0, ), > > ...RETRY->BaselineOfZTimestamp > ...RETRY->BaselineOfZTimestamp > ...FAILED->BaselineOfZTimestamp[31mCould not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /home/travis/smalltalkCI-master/_builds/package-cache filetree:///home/travis/build/svenvc/ztimestamp/repository > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: > > and extra failures for 7.0 ! > > Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] > Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] > Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] > Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] > Loading baseline of BaselineOfMetacello...MetacelloNameNotDefinedError: project group, or package named: 'FileTree' not found when used in requires: or includes: field of package: 'Metacello-FileTree' for version: baseline of BaselineOfMetacello. > MetacelloNameNotDefinedError > > >> Peter >> >> On Tue, Oct 2, 2018 at 4:53 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi, >> >> I managed to get successful BaselineOf builds out of a GitHub in Tonel format for Pharo 7 (64 & 32 bits) and Pharo 6.1 using Travis CI and smalltalkCI. >> >> However, this does not seem to work for Pharo 6 or 5. Is this to be expected ? >> >> You can see a build failure here: >> >> https://travis-ci.org/svenvc/ztimestamp/builds/436146649 >> >> If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? This is of course related to my previous question about the reach of Tonel/github. >> >> Thx, >> >> Sven > >

Oct. 2, 2018

Re: [Pharo-dev] Tonel support for Travis CI smalltalkCI for Pharo < 6.1

by Sven Van Caekenberghe

> On 2 Oct 2018, at 17:11, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? > > Tonel is not in <P6.1. You can try to add > > #useLatestMetacello : true, > > to your smalltalkci.ston file, but I believe smalltalkCI actually uses iceberg to load tonel projects... which would be much harder to backport. > > But try with #useLatestMetacello and let us know. Thanks for your reply. That does not seem to work (same result for 6.0 and 5.0, ), ...RETRY->BaselineOfZTimestamp ...RETRY->BaselineOfZTimestamp ...FAILED->BaselineOfZTimestamp[31mCould not resolve: BaselineOfZTimestamp [BaselineOfZTimestamp] in /home/travis/smalltalkCI-master/_builds/package-cache filetree:///home/travis/build/svenvc/ztimestamp/repository MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: and extra failures for 7.0 ! Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] Fetched -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] Loaded -> BaselineOfMetacello-CompatibleUserName.1526690791 --- https://github.com/Metacello/metacello.git[master] --- https://github.com/Metacello/metacello.git[master] Loading baseline of BaselineOfMetacello...MetacelloNameNotDefinedError: project group, or package named: 'FileTree' not found when used in requires: or includes: field of package: 'Metacello-FileTree' for version: baseline of BaselineOfMetacello. MetacelloNameNotDefinedError > Peter > > On Tue, Oct 2, 2018 at 4:53 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > I managed to get successful BaselineOf builds out of a GitHub in Tonel format for Pharo 7 (64 & 32 bits) and Pharo 6.1 using Travis CI and smalltalkCI. > > However, this does not seem to work for Pharo 6 or 5. Is this to be expected ? > > You can see a build failure here: > > https://travis-ci.org/svenvc/ztimestamp/builds/436146649 > > If this does not work, does that then mean that for those versions of Pharo, they cannot load Tonel projects ? This is of course related to my previous question about the reach of Tonel/github. > > Thx, > > Sven

Oct. 2, 2018