- Pharo-dev - lists.pharo.org

Fwd: Help Needed! Survey on developer knowledge of Breakpoints/Watchpoints

by Thomas Dupriez

Hi all, As part of a research work on watchpoints, we are setting up a survey to gauge the general knowledge developers have on breakpoints/watchpoints. It should take around 10 minutes to complete. Here is the link to participate if you would be so kind: https://forms.gle/eK4HFvU1YNZZkiaHA If you are interested in the results, you can check the box at the end of the survey and we will send you feedback on the results of the survey. Additionally, we are going to set up a controlled experiment to evaluate the effectiveness of a new type of watchpoints we are developing for Pharo. The gist of it is that we will observe participants hunt some bugs, with and without the new tool, and see if their performance improve. So, if you know how to program in Pharo, and would be willing to participate, there is a question in the survey to tell us you are interested. We will get research data, and you will get a new debugging tool in Pharo. So it's a win-win. That's it! Thanks for your time! And extra thanks if you take the survey or consider participating in the experiment! Thomas Dupriez This research work is conducted by: - Eduardo A. Fontana, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Canada. - Thomas Dupriez, Univ. Lille, France. And is supervised by: - Fabio Petrillo, UniversitÃ© du QuÃ©bec Ã Chicoutimi, Chicoutimi, QuÃ©bec, Canada. - Steven Costiou, Inria Lille, France. - *Yann-GaÃ«l GuÃ©hÃ©neuc*, Concordia University, Montreal, Quebec, Canada. - *StÃ©phane Ducasse*, Inria Lille, France.

June 10, 2020

[Pharo 9.0] Build #350: 6530-Job-progress-bar-is-under-the-bar

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

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

June 10, 2020

[Pharo 9.0] Build #349: 6527-Rule-Super-and-Self-Messages-sent-but-not-implemented-is-bogus

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

There is a new Pharo build available! The status of the build #349 was: FAILURE. The Pull Request #6535 was integrated: "6527-Rule-Super-and-Self-Messages-sent-but-not-implemented-is-bogus" Pull request url: https://github.com/pharo-project/pharo/pull/6535 Issue Url: https://github.com/pharo-project/pharo/issues/6527 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #348: Unify Slots and LiteralVariable in single hierarchy

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

There is a new Pharo build available! The status of the build #348 was: SUCCESS. The Pull Request #6522 was integrated: "Unify Slots and LiteralVariable in single hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/6522 Issue Url: https://github.com/pharo-project/pharo/issues/variableRefactor Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 10, 2020

[Pharo 9.0] Build #347: [Disable Flaky Tests] Disable two Zinc flaky tests

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

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…

June 10, 2020

Re: [Pharo-dev] should doubleclicking on symbol select # too?

by Chris Muller

Symbols are often used as arguments to #perform:, I don't know if Pharo ignores the initial hashmark (#) to allow browsing implementors but, if not, that could be a reason.. :) - Chris On Tue, Jun 9, 2020 at 2:26 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 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 10, 2020

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