- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #497: 3882-improve-testslotUsers
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #497 was: SUCCESS. The Pull Request #3947 was integrated: "3882-improve-testslotUsers" Pull request url: https://github.com/pharo-project/pharo/pull/3947 Issue Url: https://github.com/pharo-project/pharo/issues/3882 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #496: 3882-improve-testslotUsers
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #496 was: FAILURE. The Pull Request #3947 was integrated: "3882-improve-testslotUsers" Pull request url: https://github.com/pharo-project/pharo/pull/3947 Issue Url: https://github.com/pharo-project/pharo/issues/3882 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #495: LanguageEnvironment and Locale[ID]
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #495 was: FAILURE. The Pull Request #3832 was integrated: "LanguageEnvironment and Locale[ID]" Pull request url: https://github.com/pharo-project/pharo/pull/3832 Issue Url: https://github.com/pharo-project/pharo/issues/LanguageEnvironment_LocaleID Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #163: [Backport]3437-Adding-an-instance-class-variable-remove-the-traits-of-a-class
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #163 was: FAILURE. The Pull Request #3438 was integrated: "[Backport]3437-Adding-an-instance-class-variable-remove-the-traits-of-a-class" Pull request url: https://github.com/pharo-project/pharo/pull/3438 Issue Url: https://pharo.fogbugz.com/f/cases/3437 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 2

[Pharo 7.0] Build #164: Backport of fix for diamond problem in traits with slots.
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #164 was: FAILURE. The Pull Request #3736 was integrated: "Backport of fix for diamond problem in traits with slots." Pull request url: https://github.com/pharo-project/pharo/pull/3736 Issue Url: https://pharo.fogbugz.com/f/cases/backporting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #494: 3198-WaitfreeQeuenextOrNilSuchThat-memory-leak
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #494 was: FAILURE. The Pull Request #3205 was integrated: "3198-WaitfreeQeuenextOrNilSuchThat-memory-leak" Pull request url: https://github.com/pharo-project/pharo/pull/3205 Issue Url: https://github.com/pharo-project/pharo/issues/3198 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

SessionErrorHandlingTest UI lockup
by Ben Coman July 15, 2019

July 15, 2019

In Pharo 80482 I am experiencing a UI lockup running... SessionErrorHandlingTest>>testErrorCaughtAndDefferedIfExceptionSignaledAtStartupWhenStartupUiManagerActive Can anyone else confirm? cheers -ben

2 1

proposal - contribution workflow - PR-only for pre-fixed Issues
by Ben Coman July 15, 2019

July 15, 2019

Some improvements are often discovered, fixed and submitted all in the same moment - prior to their being an existing Issue logged. When we were using MCZ files that had no facility to hang a discussion on them, it was a good policy that **every** contribution required an Issue as a place for discussion and approval. However we are now using Pull Requests that provide such a facility for discussion and approval. There is not much difference between an "Issue" and a "PR" - indeed their index numbers are interleaved. So when we already have a PR ready to go, it seems redundant to first create an matching Issue just to have something to close. It seems particularly redundant when an Issues is created and closed within the same hour a PR is submitted and unnecessary double-handling. So I propose that pre-fixed-issues that a submitted with a code contribution require a PR-only and "Issues" are left for reports without an immediate fix that require longer term visibility. cheers -ben P.S. Thank you Torsten for your stream of small fixes. [image: x.png]

4 3

[ANN] Pharo Newsletter June 2019
by Marcus Denker July 15, 2019

July 15, 2019

The Pharo Newsletter for June 2019 was send to subscribers. It is now available online: https://mailchi.mp/pharo/pharo-newsletter-june-2019 Find all the older newsletters in the archive: http://newsletter.pharo.org. You can subscribe to get the newsletter to get it as soon as is released. The July newsletter will be out soon (this week) Marcus

1 0

[Pharo 8.0] Build #493: 3897-unify-name-of-RGMethodDefinition-and-CompiledMethod
by ci-pharo-ci-jenkins2＠inria.fr July 15, 2019

July 15, 2019

There is a new Pharo build available! The status of the build #493 was: FAILURE. The Pull Request #3909 was integrated: "3897-unify-name-of-RGMethodDefinition-and-CompiledMethod" Pull request url: https://github.com/pharo-project/pharo/pull/3909 Issue Url: https://github.com/pharo-project/pharo/issues/3897 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0