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

[Pharo 7.0-dev] Build #472: 21090 Super tearDown need to be called as last message in tearDown of Monticello

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

There is a new Pharo build available! The status of the build #472 was: SUCCESS. The Pull Request #768 was integrated: "21090 Super tearDown need to be called as last message in tearDown of Monticello" Pull request url: https://github.com/pharo-project/pharo/pull/768 Issue Url: https://pharo.fogbugz.com/f/cases/21090 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

Re: [Pharo-dev] CI Hickups ...

by Marcus Denker

> On 26 Jan 2018, at 15:06, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 26 Jan 2018, at 14:42, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >> >> >> >>> On Jan 26, 2018, at 09:13, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Hello, >>> >>> Yesâ¦ I try to make notes about all failing test so we can detect patterns >>> >> >> Will you share the notes? >> > > Here are some from todays reviews: > > testPatch â MacOS32.Zinc.Tests.ZnClientTests > Failed to start server on port 1719. Is there one already? > > > testTwiceDeliveredDataSholdBeDetected â MacOS32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > testTwiceDeliveredDataSholdBeDetected â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > testDeliverNow3 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > testDeliverNow2 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > testAddCollector3 â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > testNotDeliveredDataShouldBeResent â Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest > > > testGetPharoVersion â MacOS32.Zinc.Zodiac.ZnHTTPSTests > > testExecuteOnceAfterSchedulingMultipleTimes â MacOS32.OmbuTests.OmDeferrerTest > More interesting data points: -> end of the week (Friday to Sunday) most of the fails happened due to the macOS Slave being not in a good state. I killed the virtual server and re-created it sunday evening -.> after that, we got quite a lot of successful green CI runs. As this is Sunday, my guess is that the load on the CI infrastructure is fairly low. ==> what we need to do: 1) dead infrastructure cases need to be detected somehow. 2) the CI infrastructure overload seems to be the root of the problem to some extend. Marcus

Jan. 28, 2018

[Pharo 7.0-dev] Build #471: 21084 Super tearDown need to be called as last message in tearDown of GT Tools

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

There is a new Pharo build available! The status of the build #471 was: SUCCESS. The Pull Request #770 was integrated: "21084 Super tearDown need to be called as last message in tearDown of GT Tools" Pull request url: https://github.com/pharo-project/pharo/pull/770 Issue Url: https://pharo.fogbugz.com/f/cases/21084 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

[Pharo 7.0-dev] Build #470: 21089 Super tearDown need to be called as last message in tearDown of Versionner tests

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

There is a new Pharo build available! The status of the build #470 was: FAILURE. The Pull Request #763 was integrated: "21089 Super tearDown need to be called as last message in tearDown of Versionner tests" Pull request url: https://github.com/pharo-project/pharo/pull/763 Issue Url: https://pharo.fogbugz.com/f/cases/21089 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

[Pharo 7.0-dev] Build #469: 21087 Super tearDown need to be called as last message in tearDown of JobTest

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

There is a new Pharo build available! The status of the build #469 was: FAILURE. The Pull Request #765 was integrated: "21087 Super tearDown need to be called as last message in tearDown of JobTest" Pull request url: https://github.com/pharo-project/pharo/pull/765 Issue Url: https://pharo.fogbugz.com/f/cases/21087 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

[Pharo 7.0-dev] Build #468: 21082 Super tearDown need to be called as last message in tearDown of Glamour tests

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

There is a new Pharo build available! The status of the build #468 was: FAILURE. The Pull Request #769 was integrated: "21082 Super tearDown need to be called as last message in tearDown of Glamour tests" Pull request url: https://github.com/pharo-project/pharo/pull/769 Issue Url: https://pharo.fogbugz.com/f/cases/21082 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

[Pharo 7.0-dev] Build #467: 21097 Super tearDown need to be called as last message in tearDown of Morphic tests

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

There is a new Pharo build available! The status of the build #467 was: FAILURE. The Pull Request #764 was integrated: "21097 Super tearDown need to be called as last message in tearDown of Morphic tests" Pull request url: https://github.com/pharo-project/pharo/pull/764 Issue Url: https://pharo.fogbugz.com/f/cases/21097 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 28, 2018

Re: [Pharo-dev] How to add a new rule?

by Yuriy Tymchuk

Hi Stef. First of all, please include my email in the recipients list. Iâm committed to maintain the Rule infrastructure, but I rarely manage to read through Pharo dev. I was nice that Myroslava told me about this email. Secondly I suppose that you are working on Pharo 7, because Pharo 6 mostly follows the old approach. One thing that can cause a rule not showing up is caching, and although it should be automatically invalidated upon the addition of a new rule, you can manually clear it by searching for âRenrakuâ in settings and pressing the âReset rule cacheâ button. You should not subclass RBTransformationRule, you should subclass ReNodeRewriteRule. In fact if you check, there are no subclasses of RBTransformationRule. Now about documentation. I suspect that my IWST presentation and the Renraku paper (Thesis chapter) are not enough, but the problem is that nobody tried to create rules and give me a feedback about that so far. As you are adding new rules, I think that this is a nice opportunity to write some kind of a booklet, because rules are really powerful and we should share the knowledge of how to create them (and we should also simplify the creation process). Right now there is a âRenraku Quality Rulesâ help group in the main Pharo help browser that provides a brief description of how to create rules and run them. I think that this is a good starting point because I tried to put there the essential information needed to start with rule creation. P.S. what would be nice is to generate booklets from Pharo help, because I does not make sense to have 2 sources of documentation. Cheers. Uko > On 27 Jan 2018, at 16:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi yuriy > > We defined a new rule subclass of RBTransformationRule and we did not > get why the rule > was not taken into account. > > We put an halt in another class such as ifNotNilDo: in > - initialize (is there a cache)? > - checkMethod: > > and it did not stop. > We started to > to watch your ESUG videos > to read your PhD > > but it did not help us. > > Stef >

Jan. 28, 2018

How to add a new rule?

by Stephane Ducasse

Hi yuriy We defined a new rule subclass of RBTransformationRule and we did not get why the rule was not taken into account. We put an halt in another class such as ifNotNilDo: in - initialize (is there a cache)? - checkMethod: and it did not stop. We started to to watch your ESUG videos to read your PhD but it did not help us. Stef

Jan. 27, 2018

[Pharo 7.0-dev] Build #465: 21166-Make-Glamour-Example-Browser-searchable

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

There is a new Pharo build available! The status of the build #465 was: SUCCESS. The Pull Request #748 was integrated: "21166-Make-Glamour-Example-Browser-searchable" Pull request url: https://github.com/pharo-project/pharo/pull/748 Issue Url: https://pharo.fogbugz.com/f/cases/21166 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 27, 2018