- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #347: [Disable Flaky Tests] Disable two Zinc flaky tests
by ci-pharo-ci-jenkins2＠inria.fr June 10, 2020

June 10, 2020

There is a new Pharo build available! The status of the build #347 was: SUCCESS. The Pull Request #6497 was integrated: "[Disable Flaky Tests] Disable two Zinc flaky tests" Pull request url: https://github.com/pharo-project/pharo/pull/6497 Issue Url: https://github.com/pharo-project/pharo/issues/disableZnFlakyTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

should doubleclicking on symbol select # too?
by StÃ©phane Ducasse June 10, 2020

June 10, 2020

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

2 1

[Pharo 9.0] Build #346: [Doc]: Reflectivity - Metalink Argument and Reification Comments
by ci-pharo-ci-jenkins2＠inria.fr June 9, 2020

June 9, 2020

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…

2 1

What to do with our failing CI?
by Denis Kudriashov June 9, 2020

June 9, 2020

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

2 1

[ANN] Pharo Consortium New Academic Member: Ryerson University
by Marcus Denker June 9, 2020

June 9, 2020

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/>

1 0

[Mm10s] 2020-06-08
by Esteban Lorenzano June 8, 2020

June 8, 2020

### Last week: * [Idle-VM] w/Pablo. Worker problem with delays worker version was not interrupting the aio. We spent some time here and this was a non existing problem at the end (but we found and fix a bug on Spec2-Gtk). * [Idle-VM] problem when save&quit image with gtk backend fix a bug happening when application was shutting down and some events want still happen, who causes a callback that is alredy discarded to be executed. * [Idle-VM] new version of memory access test, bench and merge of new memory access primitive (lowcode didn't applied, finally) * [spec2] preparation of a window box to make some tests there. * [spec2] gtk backend now has an image-side based tree store, which allows much better interoperability. Next task is to migrate the adaptors: list, table and treetable (not trivial, but needed) * [TFFI] added a new type: FFIBoolean32 to handle the fact that many libraries (in my case, Gtk), do not use bool=8bit implementation. Now, users need to map their boolean (in my case, gboolean) to this type by hand. I didn't find a better way to fix this issue :( * [spec2] gtk backend now answers propertly to keyboard events in windows. * [spec2] fix a (new) bug on GtkTreeView, because we do not need to unref stores manually. This bug was introduced by my recent fix on GtkTreeView, which initialize method was not sending super. * [spec2] avoid the traverse of roots when releasing a GtkTreeDataStore (Gtk does that) * [spec2] list/table/tree migrated to use the new GtkTreeDataStore (lots of simplifications, specially on GtkTreeTableAdapter) * [NewTools-Playground] bug: doit from toolbar does not uses interactionMode * [Spec2-doc] Add style section (reference) to SpApplication * [NewTools-Playground] bug: "implementors" is not working. I couldnât reproduce the problem. Maybe is fixed now? ### This week (starting 2020-06-08): - Mostly cleanups and re-organisations on Spec2 (preparing v0.7 for Pharo9) - Preparing v0.1 of NewTools (also, to prepare an integration to Pharo9) - Building VM on Fedora linux - Testing Idle-VM on Windows

3 2

[Pharo 9.0] Build #345: add-missing-method-uffi
by ci-pharo-ci-jenkins2＠inria.fr June 8, 2020

June 8, 2020

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…

2 1

[Pharo 9.0] Build #344: enable-full-block-closures
by ci-pharo-ci-jenkins2＠inria.fr June 8, 2020

June 8, 2020

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…

1 0

[Pharo 9.0] Build #343: 6500-Cleanups
by ci-pharo-ci-jenkins2＠inria.fr June 8, 2020

June 8, 2020

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…

1 0

PROPOSAL: UN-St (United Nations of Smalltalk)
by Sean DeNigris June 8, 2020

June 8, 2020

I believe that the Squeak/Pharo/Cuis communit(ies) share one very special thing, which most of the world has completely missed, and which the world sorely needs if the true power of computing to unleash and evolve the human mind is ever to be realized: a love and appreciation for personal technological augmentation/amplification available to all as represented by the Dynabook and/or its prototype software (Smalltalk as a concept, not any version/implementation e.g. Smalltalk-80). Like a few survivors after the sinking of Atlantis, we can pick up the remnants of this dream and resume marching toward the objective (or at least keep its memory alive until an auspicious time when it can be realized)â¦ or, like most groups of human beings throughout history who start with a common aim, we can bicker among ourselves about e.g. historical discrepancies, personal slights, and conflicting subgoals, and allow those squabbles to distract us and derail our primary mission. This would be disappointing but not surprising: it is how every war is started. I have contributed, hacked, conferenced, and visited with many members of our wider community for over a decade now and, maybe because I had the âluxuryâ of finding Smalltalk after some of the political lines had been well-drawn, I can clearly see that we are fundamentally united. I cringe every time I see cynical, caustic exchanges - both for my participating colleagues who are obviously in pain - probably exacerbated by their passion for our shared endevour - and for the counterproductive effect the antagonism is sure to have on our common goal. Virtually every exchange is between two people who I personally know to be good and competent. Here is my proposal: Letâs form an informal committee - a United Nations of Smalltalk if you will - including at least one member of each community, who will collaborate on cooperation between the dialects and mediate any friction before it boils over. Iâd be happy to participate, I guess as a representative of the Pharo community. Although I have no official role in the Pharo leadership, I have much of my professional life invested there. I often wish I had the time to keep all my projects compatible with Squeak, but I usually feel like Iâm barely keeping up as it is! I hope Iâm not alone in these feelings and look forward to the response of our community (most emphatically singular). This message is being cross-posted to Pharo-Dev, Squeak-Dev, and Cuis MLs (I think Iâm still a member of all three - fingers crossedâ¦) - Sean (DeNigris)

5 5