July 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Max Leske

Fuel: https://github.com/theseion/Fuel Seaside: https://github.com/SeasideSt/Seaside On 5 Jul 2018, at 16:31, Serge Stinckwich wrote: > On Thu, Jul 5, 2018 at 3:24 PM Julien <julien.delplanque(a)inria.fr> > wrote: > >> Hello Pharo community, >> >> I am currently working on detecting rotten tests in Pharo projects. >> >> Rotten tests are defined as test methods containing one or many >> assertions >> in their source code but one or many of these assertions are not >> executed >> when the test is run. >> To have more details on the subject, you can check the research >> report >> related to our first definition of these tests freely available on >> HAL [1]. >> >> In this context, we built a test analyser which, given a Pharo >> package >> containing tests, finds rotten tests [2]. This analyser is still >> under >> development. >> >> We would like to extend the experiment of our research report [1] and >> to >> analyse more projects in order to get a better understanding of >> rotten >> tests. >> >> To do that, we need your help. You can help us in two ways: >> 1. Answer this email with links to one or many open-source Pharo >> projects >> containing tests. >> > > âWe have 774 tests in PolyMath: > https://github.com/PolyMathOrg/PolyMath > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally > for > machines to execute."http://www.doesnotunderstand.org/

July 5, 2018

Re: [Pharo-dev] Need help to get a list of Pharo projects with tests

by Serge Stinckwich

On Thu, Jul 5, 2018 at 3:24 PM Julien <julien.delplanque(a)inria.fr> wrote: > Hello Pharo community, > > I am currently working on detecting rotten tests in Pharo projects. > > Rotten tests are defined as test methods containing one or many assertions > in their source code but one or many of these assertions are not executed > when the test is run. > To have more details on the subject, you can check the research report > related to our first definition of these tests freely available on HAL [1]. > > In this context, we built a test analyser which, given a Pharo package > containing tests, finds rotten tests [2]. This analyser is still under > development. > > We would like to extend the experiment of our research report [1] and to > analyse more projects in order to get a better understanding of rotten > tests. > > To do that, we need your help. You can help us in two ways: > 1. Answer this email with links to one or many open-source Pharo projects > containing tests. > âWe have 774 tests in PolyMath: https://github.com/PolyMathOrg/PolyMath -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

July 5, 2018

Need help to get a list of Pharo projects with tests

by Julien

Hello Pharo community, I am currently working on detecting rotten tests in Pharo projects. Rotten tests are defined as test methods containing one or many assertions in their source code but one or many of these assertions are not executed when the test is run. To have more details on the subject, you can check the research report related to our first definition of these tests freely available on HAL [1]. In this context, we built a test analyser which, given a Pharo package containing tests, finds rotten tests [2]. This analyser is still under development. We would like to extend the experiment of our research report [1] and to analyse more projects in order to get a better understanding of rotten tests. To do that, we need your help. You can help us in two ways: 1. Answer this email with links to one or many open-source Pharo projects containing tests. 2. If you want, provide us private projects or, at least, run our analyser on these private projects and give us back the results. If you want to help us with the second option, send me a mail directly at julien.delplanque(a)inria.fr <mailto:julien.delplanque@inria.fr>. Thanks in advance. Regards, Julien Delplanque Links: [1]: https://hal.archives-ouvertes.fr/hal-01819302 <https://hal.archives-ouvertes.fr/hal-01819302> [2]: https://github.com/juliendelplanque/RottenTestsFinder/ <https://github.com/juliendelplanque/RottenTestsFinder/> --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

July 5, 2018

[Pharo 7.0-dev] Build #1117: 22236-User-friendly-AnnouncergtInspectorSubscriptionsIn-extension

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

There is a new Pharo build available! The status of the build #1117 was: SUCCESS. The Pull Request #1622 was integrated: "22236-User-friendly-AnnouncergtInspectorSubscriptionsIn-extension" Pull request url: https://github.com/pharo-project/pharo/pull/1622 Issue Url: https://pharo.fogbugz.com/f/cases/22236 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 5, 2018

[Pharo 7.0-dev] Build #1116: 22220 Cleanup System-Localization

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

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

July 5, 2018

[Pharo 7.0-dev] Build #1115: 22175 senders implementors doesnt properly use the ast and cursor location

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

There is a new Pharo build available! The status of the build #1115 was: SUCCESS. The Pull Request #1578 was integrated: "22175 senders implementors doesnt properly use the ast and cursor location" Pull request url: https://github.com/pharo-project/pharo/pull/1578 Issue Url: https://pharo.fogbugz.com/f/cases/22175 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 5, 2018

[Pharo 7.0-dev] Build #1114: 22203 Categorize uncategorized classes in OS-Window-Core

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

There is a new Pharo build available! The status of the build #1114 was: SUCCESS. The Pull Request #1595 was integrated: "22203 Categorize uncategorized classes in OS-Window-Core" Pull request url: https://github.com/pharo-project/pharo/pull/1595 Issue Url: https://pharo.fogbugz.com/f/cases/22203 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 5, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Norbert Hartl

Ok, I think Iâve found something. If you look at the screenshot (that is my image from jenkins, 6.1 with my code loaded and that throw the error) you can see that Zinc-FileSystem.15 is already loaded. But the Author gives the hint that this was loaded by the image integrator. And it differs from the .15 from Svenâs repo. Exactly the difference that could cause my error. Iâm not sure if metacello upgrades only packages that have a higher version number. But that would be the explanation why it doesnât work for me. I checked it by download a fresh 6.1 image and the situation is the same here. So reproducing the problem should be as easy as creating a baseline that loads zinc 2.9.2 and later something from github. My case was that in the first step the project code was loaded in the image including zinc 2.9.2. That image was saved and on the next invocation it loads the test code and parasol was the first dependency to load from github and it failed. Norbert > Am 05.07.2018 um 08:44 schrieb Max Leske <maxleske(a)gmail.com>: > > On 4 Jul 2018, at 23:00, Norbert Hartl wrote: > >>> Am 04.07.2018 um 17:52 schrieb Max Leske <maxleske(a)gmail.com>: >>> >>> Hi Norbert, >>> >>> Where can I get my hands on that image that you say has no sender of #newBinaryFileNamed:do: in it? >>> >> I cannot give away the image, sorry. I can try to reproduce it somehow. >> Do you expect the method to be there? > > I would have, yes. But as you have discovered, the problem may lie with ZnFileSystemUtils (although I would have expected that package to be updated along with Zinc). > > Max > >> >> Norbert >>> Max >>> >>>> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >>>> >>>> I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log >>>> >>>> Loading baseline of BaselineOfMobilityMap... >>>> ...RETRY->BaselineOfParasol >>>> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: >>>> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: >>>> ZnClient>>downloadEntityTo: >>>> ZnClient>>downloadTo: >>>> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >>>> >>>> The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. >>>> >>>> I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. >>>> >>>> Any ideas? >>>> >>>> Norbert >>> >

July 5, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Max Leske

On 4 Jul 2018, at 23:00, Norbert Hartl wrote: >> Am 04.07.2018 um 17:52 schrieb Max Leske <maxleske(a)gmail.com>: >> >> Hi Norbert, >> >> Where can I get my hands on that image that you say has no sender of >> #newBinaryFileNamed:do: in it? >> > I cannot give away the image, sorry. I can try to reproduce it > somehow. > Do you expect the method to be there? I would have, yes. But as you have discovered, the problem may lie with ZnFileSystemUtils (although I would have expected that package to be updated along with Zinc). Max > > Norbert >> Max >> >>> On 4 Jul 2018, at 17:30, Norbert Hartl wrote: >>> >>> I tried to see how hard it would be to load my current project in >>> pharo7. Cyril helped me to see that I load an old version of zinc >>> and it does not work that way. Upgrading to zinc 2.9.2 made it work >>> in pharo 7 but my jenkins build do not work anymore. I donât fully >>> understand what is happening. I see in the log >>> >>> Loading baseline of BaselineOfMobilityMap... >>> ...RETRY->BaselineOfParasol >>> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: >>> ZnFileSystemUtils class>>newBinaryFileNamed:do: >>> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: >>> #newBinaryFileNamed:do: >>> ZnClient>>downloadEntityTo: >>> ZnClient>>downloadTo: >>> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >>> >>> The strange thing about it is that when I download that image where >>> the error occurred I cannot find a sender of #newBinaryFileNamed:do: >>> and the #downloadEntityTo: does not seem to use it. Downgrading to >>> zinc 2.8.10 makes it work again. >>> >>> I feel a little bit stupid because the image does not load any new >>> package on startup and still there is this error message which does >>> not make sense to me at all. >>> >>> Any ideas? >>> >>> Norbert >>

July 5, 2018

Re: [Pharo-dev] Problem with zinc 2.9.2

by Norbert Hartl

> Am 04.07.2018 um 19:34 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > How exactly did you load ? > > On macOS Pharo-7.0+alpha.build.1099.sha.bcfa81fa7b35214eede30962d35d1d547c199989 (64 Bit) I went to the Catalog and loaded the default stable version. > > Fetched -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ > Loaded -> ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.115 --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ --- http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo70/main/ > Loading 2.9.2 of ConfigurationOfZincHTTPComponents... > Fetched -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac > Fetched -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac > Fetched -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- http://mc.stfx.eu/Zodiac > Fetched -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Fetched -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- http://mc.stfx.eu/ZincHTTPComponents > Loaded -> Zodiac-Core-TorstenBergmann.48 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache > Loaded -> Zodiac-Tests-SvenVanCaekenberghe.22 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache > Loaded -> Zodiac-Extra-SvenVanCaekenberghe.8 --- http://mc.stfx.eu/Zodiac --- /Users/sven/Develop/Pharo/Pharo-Daily/2018-06-29/pharo-local/package-cache > Loaded -> Zinc-Character-Encoding-Core-SvenVanCaekenberghe.64 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.43 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Resource-Meta-Core-SvenVanCaekenberghe.68 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.38 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-FileSystem-SvenVanCaekenberghe.15 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-HTTP-SvenVanCaekenberghe.474 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Tests-SvenVanCaekenberghe.245 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Zodiac-SvenVanCaekenberghe.44 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > Loaded -> Zinc-Resource-Meta-FileSystem-SvenVanCaekenberghe.9 --- http://mc.stfx.eu/ZincHTTPComponents --- cache > ...finished 2.9.2 > > All unit tests 411 were green. > > #newBinaryFileNamed:do: can be found on the class side of ZnFileSystemUtils and is used by ZnClient>>#downloadEntityTo: > Really? In my image I donât have it. Iâm loading it in 6.1. Ok so it seems that the zinc was updated but ZnFileSystemUtils not. Need to check. Norbert >> On 4 Jul 2018, at 17:30, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I tried to see how hard it would be to load my current project in pharo7. Cyril helped me to see that I load an old version of zinc and it does not work that way. Upgrading to zinc 2.9.2 made it work in pharo 7 but my jenkins build do not work anymore. I donât fully understand what is happening. I see in the log >> >> Loading baseline of BaselineOfMobilityMap... >> ...RETRY->BaselineOfParasol >> ...RETRY->BaselineOfParasol[31mMessageNotUnderstood: ZnFileSystemUtils class>>newBinaryFileNamed:do: >> [0mZnFileSystemUtils class(Object)>>doesNotUnderstand: #newBinaryFileNamed:do: >> ZnClient>>downloadEntityTo: >> ZnClient>>downloadTo: >> IceMetacelloPharoPlatform(MetacelloPharoPlatform)>>downloadZipArchive:to: >> >> >> The strange thing about it is that when I download that image where the error occurred I cannot find a sender of #newBinaryFileNamed:do: and the #downloadEntityTo: does not seem to use it. Downgrading to zinc 2.8.10 makes it work again. >> >> I feel a little bit stupid because the image does not load any new package on startup and still there is this error message which does not make sense to me at all. >> >> Any ideas? >> >> Norbert > >

July 4, 2018