June 2020 - Pharo-dev - lists.pharo.org

should doubleclicking on symbol select # too?

by StÃ©phane Ducasse

Hi I would like to know what you think about the doubleclick selection on symbol? Right now #foo selection will only select foo and I do not see why this is positif. In the past I fixed that the selection of :each selects the : was NOT selected too so that we can access the value of the argument in a single click and now it is so good that we do not even see it. So may we should do the same for #foo but in the other way. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

June 9, 2020

Re: [Pharo-dev] [Pharo 9.0] Build #346: [Doc]: Reflectivity - Metalink Argument and Reification Comments

by Sean P. DeNigris

ci-pharo-ci-jenkins2 wrote > The Pull Request #6525 was integrated Less than 5 hours from Discord question to fix integration - not a bad turnaround ha ha! From PR submission to merge was less than 2 hours :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 9, 2020

[Pharo 9.0] Build #346: [Doc]: Reflectivity - Metalink Argument and Reification Comments

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

There is a new Pharo build available! The status of the build #346 was: SUCCESS. The Pull Request #6525 was integrated: "[Doc]: Reflectivity - Metalink Argument and Reification Comments" Pull request url: https://github.com/pharo-project/pharo/pull/6525 Issue Url: https://github.com/pharo-project/pharo/issues/doc/metalink Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 9, 2020

Re: [Pharo-dev] What to do with our failing CI?

by Marcus Denker

Hi, Yes, I like the idea. There is the downside that it might take pressure away from fixing issues that are behind. For the current problem, Pablo found out that it has to do with some network issue that the admins will fix. So here it makes sense to now put the test on skip as we know what the reason for the failure is (and that it will be fixed). Marcus > On 7 Jun 2020, at 17:23, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hello. > > We have a failing CI for quite a long time (maybe few months). And out of that there are always new flaky tests failing our PRs time to time. We did fix some of them but I do not think it is possible to avoid them at all. > > I propose a simple approach/convention to quickly recover CI from such appearing intermittent problems. When we detect a flaky test let's do two simple PRs: > > 1. [Disable Flaky Test] PR will skip problem tests and flag them to be easily found in the image. > testWithIntermitentIssue > self flag: #flakyTest > self skip. > "the rest of test code" > This PR is supposed to be quickly merged to avoid failures in new PRs > > 2. [Enable Flaky Test] PR will enable tests back. > It will record the issue and track the current "flaky state". > > For example I created two PRs for Zinc tests: > - [Disable Flaky Tests] Disable two Zinc flaky tests <https://github.com/pharo-project/pharo/pull/6497> > - [Enable Flaky Tests] Enable two Zinc flaky tests <https://github.com/pharo-project/pharo/pull/6498> > The enable PR here will be always red until we integrate a fix. > > Of course some issues are trivial to fix like increasing the allowed time for the test. And we should just push the fix. But when it is not clear what to do it is better to remove the case from the overall CI and localize the issue in concrete PR. So expert devs could look at the problem without interrupting the contribution of other people. > > I think it's a very easy approach to follow by anyone. And it can be even automated. > That's my idea. > Best regards, > Denis >

June 9, 2020

[ANN] Pharo Consortium New Academic Member: Ryerson University

by Marcus Denker

The Pharo Consortium is very happy to announce that the Ryerson University has joined the Consortium as an Academic Member. About - Ryerson University: https://www.ryerson.ca <https://www.ryerson.ca/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org <http://association.pharo.org/>

June 9, 2020

Re: [Pharo-dev] [Mm10s] 2020-06-08

by Sean P. DeNigris

tesonep(a)gmail.com wrote > - Missing parts in the Image to have Sista + FullBlockClosure. Yay! Thanks :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 8, 2020

Re: [Pharo-dev] [Pharo 9.0] Build #345: add-missing-method-uffi

by Sean P. DeNigris

ci-pharo-ci-jenkins2 wrote > Issue Url: https://github.com/pharo-project/pharo/issues/add The issue link in this report seems to be broken ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

June 8, 2020

[Pharo 9.0] Build #345: add-missing-method-uffi

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

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

June 8, 2020

[Pharo 9.0] Build #344: enable-full-block-closures

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

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

June 8, 2020

[Pharo 9.0] Build #343: 6500-Cleanups

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

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

June 8, 2020