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

How to update currently used VM for PharoLauncher?

by stephan

I've noticed a few VM updates I want to use with PharoLauncher. What is the currently recommended way to update my PharoLauncher to use a non-stable version? Stephan

Nov. 3, 2017

[Pharo 7.0-dev] Build #257: 20632-Rename-PluggableSortFunction-to-CollatorBlockFunction

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

There is a new Pharo build available! The status of the build #257 was: SUCCESS. The Pull Request #430 was integrated: "20632-Rename-PluggableSortFunction-to-CollatorBlockFunction" Pull request url: https://github.com/pharo-project/pharo/pull/430 Issue Url: https://pharo.fogbugz.com/f/cases/20632 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017

[Pharo 7.0-dev] Build #256: 20633-Update-Tonel-version

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

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

Nov. 3, 2017

[Pharo 7.0-dev] Build #255: 20629-wrong-FuelPlatform-Pharo-Core-package-loading

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

There is a new Pharo build available! The status of the build #255 was: SUCCESS. The Pull Request #429 was integrated: "20629-wrong-FuelPlatform-Pharo-Core-package-loading" Pull request url: https://github.com/pharo-project/pharo/pull/429 Issue Url: https://pharo.fogbugz.com/f/cases/20629 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017

[Pharo 7.0-dev] Build #254: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

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

There is a new Pharo build available! The status of the build #254 was: FAILURE. The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" Pull request url: https://github.com/pharo-project/pharo/pull/426 Issue Url: https://pharo.fogbugz.com/f/cases/20628 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

by Pavel Krivanek

It was a strange failure during the image cleanup, I guess it was related to the FuelPlatform-Pharo-Core package issue which is now fixed. -- Pavel 2017-11-03 13:48 GMT+01:00 Norbert Hartl <norbert(a)hartl.name>: > Maybe that is the reason the status is considered a FAILURE? > > Norbert > > > Am 03.11.2017 um 13:44 schrieb Torsten Bergmann <astares(a)gmx.de>: > > > > This build number is red: > > > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/ > > > > > >> Gesendet: Freitag, 03. November 2017 um 13:16 Uhr > >> Von: ci-pharo-ci-jenkins2(a)inria.fr > >> An: pharo-dev(a)lists.pharo.org > >> Betreff: [Pharo-dev] [Pharo 7.0-dev] Build #253: > 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings > >> > >> There is a new Pharo build available! > >> > >> The status of the build #253 was: FAILURE. > >> > >> The Pull Request #426 was integrated: "20628-Categories-definition- > in-exported-Tonel-must-be-symbols-not-strings" > >> Pull request url: https://github.com/pharo-project/pharo/pull/426 > >> > >> Issue Url: https://pharo.fogbugz.com/f/cases/20628 > >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% > 20pull%20request%20and%20branch%20Pipeline/job/development/253/ > >> > >

Nov. 3, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

by Norbert Hartl

Maybe that is the reason the status is considered a FAILURE? Norbert > Am 03.11.2017 um 13:44 schrieb Torsten Bergmann <astares(a)gmx.de>: > > This build number is red: > > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > > >> Gesendet: Freitag, 03. November 2017 um 13:16 Uhr >> Von: ci-pharo-ci-jenkins2(a)inria.fr >> An: pharo-dev(a)lists.pharo.org >> Betreff: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings >> >> There is a new Pharo build available! >> >> The status of the build #253 was: FAILURE. >> >> The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" >> Pull request url: https://github.com/pharo-project/pharo/pull/426 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/20628 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >>

Nov. 3, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

by Torsten Bergmann

This build number is red: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > Gesendet: Freitag, 03. November 2017 um 13:16 Uhr > Von: ci-pharo-ci-jenkins2(a)inria.fr > An: pharo-dev(a)lists.pharo.org > Betreff: [Pharo-dev] [Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings > > There is a new Pharo build available! > > The status of the build #253 was: FAILURE. > > The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" > Pull request url: https://github.com/pharo-project/pharo/pull/426 > > Issue Url: https://pharo.fogbugz.com/f/cases/20628 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… >

Nov. 3, 2017

[Pharo 7.0-dev] Build #253: 20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings

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

There is a new Pharo build available! The status of the build #253 was: FAILURE. The Pull Request #426 was integrated: "20628-Categories-definition-in-exported-Tonel-must-be-symbols-not-strings" Pull request url: https://github.com/pharo-project/pharo/pull/426 Issue Url: https://pharo.fogbugz.com/f/cases/20628 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 3, 2017

Re: [Pharo-dev] Debugger "reporting" feature

by Ben Coman

cool. done. https://pharo.fogbugz.com/f/cases/20631/debugger-copy-stack-to-clipboard cheers -ben On Fri, Nov 3, 2017 at 1:03 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Can you open a bug entry? > > On Thu, Nov 2, 2017 at 4:16 PM, Ben Coman <btc(a)openinworld.com> wrote: > > sounds good. > > cheers -ben > > > > On Thu, Nov 2, 2017 at 10:55 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > > wrote: > >> > >> Maybe we should name and implement it as "copy stack to clipboard"? > >> > >> 2017-11-02 13:19 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > >>> > >>> I've never used it to auto-report to any remote remote server. That > part > >>> can go. > >>> But as I stated, I do find it useful for getting a text representation > of > >>> the stack for manually pasting into fogbugz issues, instead of having > to dig > >>> through the halos into the morph contents. > >>> Can this part be kept and moved into the stack-context-menu? > >>> > >>> cheers -ben > >>> > >>> On Thu, Nov 2, 2017 at 5:59 PM, Denis Kudriashov <dionisiydk(a)gmail.com > > > >>> wrote: > >>>> > >>>> I think it is outdated feature and we should remove it to not confuse > >>>> people. > >>>> > >>>> 2017-11-02 9:10 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > >>>>> > >>>>> Is this functionality actuaat part can golly used? Where do the > reports > >>>>> end up? What is contained in the report? > >>>>> > >>>>> Peter > >>>>> > >>>>> On Thu, Nov 2, 2017 at 4:35 AM, Ben Coman <btc(a)openinworld.com> > wrote: > >>>>>> > >>>>>> In the Pre-Debug window there is the <Report> button that coverts > the > >>>>>> call stack to text that can be pasted into an email. But when you > proceed > >>>>>> into the main debugger it seems you lose access to that feature. > >>>>>> > >>>>>> Would it be worth adding <Report> to the debugger context menu? > >>>>>> > >>>>>> cheers -ben > >>>>> > >>>>> > >>>> > >>> > >> > > > >

Nov. 3, 2017