- Pharo-dev - lists.pharo.org

Release test for unused temps and other

by Torsten Bergmann

Hi, the very nice contribution on GIFReadWriter/animated images (see https://pharo.manuscript.com/f/cases/22137) unfortunately introduced some methods that had no sender, were uncategorized and had unused temporary variables, etc. Something that is meanwhile shown by our tools and easy to fix. I guess it was some overseen leftover. Unfortunately this also slipped through the integration process as it was merged without an approval from a community reviewer. I dont want to lament too much on this specifc case (especially as I now fixed it in https://pharo.fogbugz.com/f/cases/22426) But after I cleaned the P7 image this spring to not have unused temporaries anymore I was suprised to find such glitches again now. So to me it shows that we need to write more tests to detect violations and keep our achieved quality standards up and also should not solely rely on the review process. Otherwise we need to invest our time in cleaning up our own stuff afterwards again and again. To be specific one can evaluate: CompiledMethod allInstances select: [:m | m ast temporaries anySatisfy: [:x | x binding isUnused ]]. to find unused temps - which would be easy to package up into one of the release test to ensure no unused temp vars are left (the tearDown would require an "ASTCache reset"). The problem is that this simple test would take around 20-30 seconds depending on machine and I do not know if it would be a good idea/good solution to integrate. Especially I'm not sure if it is worth the issue or will kill the CI again and again. What do you think about it? Comments appreciated? Thanks T.

Sept. 6, 2018

[Pharo 7.0-dev] Build #1230: 22421 fogbugz is now manuscript

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

There is a new Pharo build available! The status of the build #1230 was: FAILURE. The Pull Request #1772 was integrated: "22421 fogbugz is now manuscript" Pull request url: https://github.com/pharo-project/pharo/pull/1772 Issue Url: https://pharo.fogbugz.com/f/cases/22421 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1229: 22419 Complete class comments in Kernel-Tests

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

There is a new Pharo build available! The status of the build #1229 was: FAILURE. The Pull Request #1770 was integrated: "22419 Complete class comments in Kernel-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1770 Issue Url: https://pharo.fogbugz.com/f/cases/22419 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1228: 22418 Cleanup DateAndTimeDosEpochTest

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

There is a new Pharo build available! The status of the build #1228 was: FAILURE. The Pull Request #1768 was integrated: "22418 Cleanup DateAndTimeDosEpochTest" Pull request url: https://github.com/pharo-project/pharo/pull/1768 Issue Url: https://pharo.fogbugz.com/f/cases/22418 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

Why being a Pharo Association Member matters?

by StÃ©phane Ducasse

Hi Pharo supporters First I would like thank you. And I would like to show you that your membership in the Pharo association is really helping Pharo. We are creating a precise report but the main message is the same. You concretely help Pharo. First, we would like to really thank you for your support because as you will see it is important. Your contributions are making an impact. Until now, the association did not make visible how was spent the money from your membership. It's time to fix this. In the first place, the support we got from last year enable the creation of monthly activities helping with the development of Pharo. The association is now the support for the following ones: Sprint organisations: Every month sprints to correct Pharo bugs are organised. You can join remotely or organise one at your location TechTalks: Every month a technical talk is been done to give visibility on Pharo process and Pharo projects and interact with the community to get feedback Next, your association contributions are securing vital Pharo infrastructures. It pays: The domains such as pharo.org. The hosting files.pharo.org: This year we moved out of Inria infrastructure because we could not identify the cause of a huge network latency. It got resolved - it was a fiber which was in bad condition but not cut. This was fixed at the level of Renater national back-bone layer, but we decided to stay outside. We plan to migrate to a better service. The wild apricot software which manages the association. It will enable us to do more with the association. (40$/month) The newsletter via Mailchimp. This newsletter is a real success with more than 2300 recipients . You get see the archive at https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486… <https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486…> (30$/month) The mailing-lists are managed with Mailname a professional service. On another note, we would like to remember the advantages of being an association member: Reduction for the PharoDays Offer access to PharoCloud (which is currently under redesign) 20% Discount on the printed book Learning Object-Oriented Programming, Design with TDD in Pharo <http://books.pharo.org/learning-oop/> Possibility to be listed as a Pharo consultant (Require gold membership) -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas 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

Sept. 6, 2018

[Pharo 7.0-dev] Build #1227: 22416 Tag Manifest in Kernel-Tests

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

There is a new Pharo build available! The status of the build #1227 was: SUCCESS. The Pull Request #1767 was integrated: "22416 Tag Manifest in Kernel-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1767 Issue Url: https://pharo.fogbugz.com/f/cases/22416 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1226: 22412-Typo-closeclosed-in-AbstractBinaryFileStream--nextputAll

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

There is a new Pharo build available! The status of the build #1226 was: SUCCESS. The Pull Request #1765 was integrated: "22412-Typo-closeclosed-in-AbstractBinaryFileStream--nextputAll" Pull request url: https://github.com/pharo-project/pharo/pull/1765 Issue Url: https://pharo.fogbugz.com/f/cases/22412 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 6, 2018

[Pharo 7.0-dev] Build #1225: 22026-Date-little-improvement-proposal-DateAndTime

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

There is a new Pharo build available! The status of the build #1225 was: SUCCESS. The Pull Request #1747 was integrated: "22026-Date-little-improvement-proposal-DateAndTime" Pull request url: https://github.com/pharo-project/pharo/pull/1747 Issue Url: https://pharo.fogbugz.com/f/cases/22026 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018

Re: [Pharo-dev] Auto-completion of methods names

by Cyril Ferlicot D.

Le 05/09/2018 Ã 10:00, Marcus Denker a Ã©critÂ : > > I will add a simpler version by default back (today). > > The old version tried to be clever and replace whole methodsâ¦ which was extremely confusing (and not really > helping). It complicated the model, too. > (We got even bug report > > Method name completion is nice, it is very easy to add method name completion back, I will do it today. > Great, thank you! I'm glad that it's not just a feature removal without replacement :) > Marcus > > -- Cyril Ferlicot https://ferlicot.fr

Sept. 5, 2018

[Pharo 7.0-dev] Build #1224: 22025-Date-little-improvement-proposal-

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

There is a new Pharo build available! The status of the build #1224 was: FAILURE. The Pull Request #1755 was integrated: "22025-Date-little-improvement-proposal-" Pull request url: https://github.com/pharo-project/pharo/pull/1755 Issue Url: https://pharo.fogbugz.com/f/cases/22025 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 5, 2018