- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #565: 21361 GTSimpleMethodsBrowser in inspector should provide titles and filter

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

There is a new Pharo build available! The status of the build #565 was: FAILURE. The Pull Request #904 was integrated: "21361 GTSimpleMethodsBrowser in inspector should provide titles and filter" Pull request url: https://github.com/pharo-project/pharo/pull/904 Issue Url: https://pharo.fogbugz.com/f/cases/21361 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 17, 2018

[Pharo 7.0-dev] Build #564: 21364 Review OrderedDictionaryTest

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

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

Feb. 17, 2018

[Pharo 7.0-dev] Build #563: 21317 remove unnecessary self run in diverse classes

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

There is a new Pharo build available! The status of the build #563 was: SUCCESS. The Pull Request #907 was integrated: "21317 remove unnecessary self run in diverse classes" Pull request url: https://github.com/pharo-project/pharo/pull/907 Issue Url: https://pharo.fogbugz.com/f/cases/21317 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018

[Pharo 7.0-dev] Build #562: 21357 cleanup formatting typos and lints in sorted collection test and related traits

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

There is a new Pharo build available! The status of the build #562 was: SUCCESS. The Pull Request #899 was integrated: "21357 cleanup formatting typos and lints in sorted collection test and related traits" Pull request url: https://github.com/pharo-project/pharo/pull/899 Issue Url: https://pharo.fogbugz.com/f/cases/21357 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018

[Pharo 7.0-dev] Build #561: 21337 - Allow to define other default folders for GTPlayBook

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

There is a new Pharo build available! The status of the build #561 was: SUCCESS. The Pull Request #881 was integrated: "21337 - Allow to define other default folders for GTPlayBook" Pull request url: https://github.com/pharo-project/pharo/pull/881 Issue Url: https://pharo.fogbugz.com/f/cases/21337 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018

[Pharo 7.0-dev] Build #560: 21358-Renraku-evaluator-creates-the-AST-of-the-methods-even-if-they-are-not-used-at-all

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

There is a new Pharo build available! The status of the build #560 was: SUCCESS. The Pull Request #901 was integrated: "21358-Renraku-evaluator-creates-the-AST-of-the-methods-even-if-they-are-not-used-at-all" Pull request url: https://github.com/pharo-project/pharo/pull/901 Issue Url: https://pharo.fogbugz.com/f/cases/21358 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #553: 20941-deprecate-theMetaclass-and-the-theNonMeta

by Alistair Grant

Hi Cyril, On 16 February 2018 at 16:59, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > On Fri, Feb 16, 2018 at 4:26 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Cyril, >> >> On 16 February 2018 at 15:57, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >>> >>> On what VM is this happening? >>> >>> For linux 64bits vm I get a lot a random crash during configuration >>> loading. But these crash vanish when using the latest Pharo 70 vm for >>> linux 64bits. >> >> Would you mind posting the output of "pharo --version" so I can try >> with exactly the same 64bit VM? > > > Hi, > > I moved our script to use the latest Pharo 70 vm but it was with the > vm we get via > > curl https://get.pharo.org/64/61+vm | bash > > It downloads a linux vm from july 2017. > > Crash happen around 50% of the time with a segfault on our Jenkins. We > have a lot of dependencies such as Famix, Seaside, MDL... So the > configurations bring *a lot* of things. I don't know if it will crash > as much with smaller configurations. I cannot share what we use since > it is close code. In your original message you said that the latest Pharo 7 64bit VM isn't crashing. Can you provide the version information for that one? Thanks, Alistair >> Thanks! >> Alistair >> > > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Feb. 16, 2018

[Pharo 7.0-dev] Build #559: 21360-Kernel-Tests-Methods-CompiledMethodTest-testSelector-produces-a-DNU

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

There is a new Pharo build available! The status of the build #559 was: FAILURE. The Pull Request #903 was integrated: "21360-Kernel-Tests-Methods-CompiledMethodTest-testSelector-produces-a-DNU" Pull request url: https://github.com/pharo-project/pharo/pull/903 Issue Url: https://pharo.fogbugz.com/f/cases/21360 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018

#valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

by Stefan Marr

Hi: I am trying to understand the different between and perhaps origin of BlockClosure>>#valueWithPossibleArgs: and BlockClosure>>#valueWithEnoughArguments: I am trying to decide which of the two I need for SOMns. The first one has seen more recent changes, when looking at the Pharo 6.1 download: valueWithPossibleArgs: anArray â> 2/12/2017 StephaneDucasse valueWithEnoughArguments: anArray â> 3/11/2001 nk While they have rather different implementations, they seem to behave identically, as far as I could tell using the following example: blocks := { [ { } ]. [:a | { a } ]. [:a :b | { a. b } ]. [:a :b :c | { a. b. c } ] }. blocks collect: [:b | b valueWithPossibleArgs: {1}]. blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. blocks collect: [:b | b valueWithEnoughArguments: {1}]. blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. I was also wondering how they relate to #cull:* One of the major differences seems to be that valueWithP* and valueWithE* are both injecting nil for absent arguments, while normal #value* and #cull* methods signal an error. Is there a specific use case why one wouldnât want to be strict here as well, but instead inject nils? Any comments or pointer appreciated. Thanks Stefan -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

Feb. 16, 2018

[Pharo 7.0-dev] Build #558: 21356-MetaLink-add-Inspector-tab-showing-definition-

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

There is a new Pharo build available! The status of the build #558 was: FAILURE. The Pull Request #900 was integrated: "21356-MetaLink-add-Inspector-tab-showing-definition-" Pull request url: https://github.com/pharo-project/pharo/pull/900 Issue Url: https://pharo.fogbugz.com/f/cases/21356 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 16, 2018