September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] argh, tests are failing!

by Pavel Krivanek

2017-09-11 12:07 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > > On Sun, Sep 10, 2017 at 7:16 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> Hi, >> >> to explain: >> >> we have lots of uncategorized methods and non commented classes. For some >> time we had to accept this ugly situation that old and legacy code. For >> Pharo 4 and 5 >> I invested a lot of time to clean this up right before the release date. >> But with 6.0 such a round was not done and in 6.0 and 6.1 it looks like a >> mess again. >> >> Why? Because we introduced new features and code and never defined a >> certain level of quality for code we include. But our initial goal with >> Pharo was (and >> hopefully still is) to cleanup things up and do better than before. >> >> So we should not forget about quality and so I spend some time last on >> this again - now for Pharo 7. For instance #setUp and #tearDown in SUnit >> should be >> in "running" as it was defined for TestCase subclasses. Also #hash and #= >> should be in "comparing" protocol. Also the goal is coming back to an image >> where >> all methods are categorized and where all classes have a comment. >> >> But for me it absolutely makes no sense to reinvest the time over and >> over into the same cleanups while others can easily make a mess again. >> >> So we should RAISE THE QUALITY BAR to ensure that we keep with such a >> quality level. Especially as see each build to be a release and the real >> release once >> a year often is more or less a snapshot. >> >> So I also wrote a new test called "ProperMethodCategorizationTest" and >> while cleaning up #hash it was green. So ProperMethodCategorizationTest >> .testHashMethodNeedsToBeInComparingProtocol >> showed no problem and I committed and have sent a Pull request. This >> looked like any other new contribution. >> > > Yes yes, I can't agree more. We need to add Lint rules running by default > also. > I will try to prepare a small tool that will collect information about health status of a build that will be stored as a STON file next to the image (at least for the development versions). Then we can generate the same information about incoming PRs and display changes. This way we will be able to see effects of the PR like what new dependencies it added, what new rules are failing and so on. It should not reject then automatically but to be a support for the PR review. -- Pavel > > >> >> What I did not knew at this time was that Iceberg code is not in git >> repository - but managed externally. So while I fixed the code in my image >> with wrongly categorized hash >> method in an Iceberg class (IceSemanticVersion) the system did not show >> me that this change did not move to GitHub. > > >> Now I know - but this has such bad side effect when we do changes and >> these packages are in the image - but not managed with the pharo repository. >> > > Yep, this should be fixed as soon as we have multiple > subdirectories/subprojects in iceberg. As soon as that is supported we will > probably move iceberg to a subtree structure as explained in here: > > https://www.slideshare.net/GuillePolito1/understanding- > the-pharo-dev-process-79632181/1 > https://github.com/guillep/PharoIntegrationProcess/wiki/ > Analysis-of-sub-project-storage-alternatives > > > >> >> Long story short: one can not fix this situation with a simple PR as >> Iceberg code is not under the "pharo" repo umbrella. >> >> I already submitted a PR for Iceberg >> >> https://github.com/pharo-vcs/iceberg/pull/458 >> >> and Esteban included that already - but only in Iceberg. We now need to >> include Iceberg. >> >> Several lessons learned from my side: >> - doing changes and having green tests in the image is not enough >> - also doing a commit and PR does not mean all of your changes are on >> GitHub >> - it is not a good situation when a part of the image code is managed >> with "pharo" repository and another part is managed externally - I see this >> as a problem of >> the new process we should discuss and address >> - we should nonetheless try to define tests to show the edges where we >> can improve and cleanup (without a test it would not have been noticed that >> while I did my best >> to cleanup the current way of managing Iceberg prevented my fix to be >> into the image in the first place) >> > > While the test is an improvement over the current situation, I ask myself > if this particular validation of the protocols shouldn't be a Renraku rule. > > >> >> I dont know what need to be done to include a new iceberg version or when >> this will happen from Estebans side - but as soon as it is done this test >> should be green again. >> > > As Pavel said, the iceberg version that is included in the system is the > one described in > > BaselineOfIDE >> loadIceberg > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:v0.5.7'; > load. > (Smalltalk classNamed: #Iceberg) enableMetacelloIntegration: true. > > So updating that method with the new iceberg version and pushing that to > Pharo should be enough. > > In any case, my mail was there just to raise the issue of the failing > tests. We should care about failing tests, and I'll cry out loud everytime > they are broken, just to make it explicit. > > >> Thanks >> T. >> >> >> Gesendet: Sonntag, 10. September 2017 um 18:24 Uhr >> Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] argh, tests are failing! >> >> Yes we know but have no idea how to recategorise Iceberg protocols >> >> On Sun, Sep 10, 2017 at 1:03 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com >> [mailto:pavel.krivanek@gmail.com]> wrote: >> >> Of course you are right, the Integrators should really take care on it. >> >> Before it were only common random failures but the main problem is with >> this PR: >> https://github.com/pharo-project/pharo/pull/264[https:// >> github.com/pharo-project/pharo/pull/264] >> >> The new test testHashMethodNeedsToBeInComparingProtocol fails on >> classIceSemanticVersion >> >> -- Pavel >> >> >> 2017-09-10 10:13 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com >> [mailto:guillermopolito@gmail.com]>: >> Hi all, >> >> Since a couple of builds we have consistently failing the following tests: >> >> >> GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test% >> 20pending%20pull%20request%20and%20branch%20Pipeline/job/ >> development/110/testReport/junit/GT.EventRecorder.Tests. >> Core/GTEventRecorderTest/testDeliverNow2/]GT.EventRecorder. >> Tests.Core.GTEventRecorderTest.testNotDeliveredDataShouldBeR >> esent[https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pendi >> ng%20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/GT.EventRecorder.Tests.Core/ >> GTEventRecorderTest/testNotDeliveredDataShouldBeResent/] >> Kernel.Tests.Processes.MutexTest.testFailedCriticalSectionSh >> ouldUnblockWaitingOne[https://ci.inria.fr/pharo-ci-jenkins2/ >> job/Test%20pending%20pull%20request%20and%20branch%20Pipelin >> e/job/development/110/testReport/junit/Kernel.Tests. >> Processes/MutexTest/testFailedCriticalSectionShouldUnblockWa >> itingOne/]ReleaseTests.Categorization.ProperMethodCat >> egorizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol/]ReleaseTests.Categorization.ProperMethodCategor >> izationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_2/]ReleaseTests.Categorization.ProperMethodCateg >> orizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_3/]ReleaseTests.Categorization.ProperMethodCateg >> orizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_4/]ReleaseTests.Categorization.ProperMethodCateg >> orizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_5/]ReleaseTests.Categorization.ProperMethodCateg >> orizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_6/]ReleaseTests.Categorization.ProperMethodCateg >> orizationTest.testHashMethodNeedsToBeInComparingProtocol[ >> https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending% >> 20pull%20request%20and%20branch%20Pipeline/job/develo >> pment/110/testReport/junit/ReleaseTests.Categorization/Pr >> operMethodCategorizationTest/testHashMethodNeedsToBeInCompar >> ingProtocol_7/ >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/testDeliverNow2/%5DGT.EventRecorder.Tests.Core.GTEventRecorderTest.testNotDeliveredDataShouldBeResent%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/testNotDeliveredDataShouldBeResent/%5DKernel.Tests.Processes.MutexTest.testFailedCriticalSectionShouldUnblockWaitingOne%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/Kernel.Tests.Processes/MutexTest/testFailedCriticalSectionShouldUnblockWaitingOne/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_2/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_3/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_4/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_5/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_6/%5DReleaseTests.Categorization.ProperMethodCategorizationTest.testHashMethodNeedsToBeInComparingProtocol%5Bhttps://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/110/testReport/junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/testHashMethodNeedsToBeInComparingProtocol_7/> >> ] >> >> >> Green builds are the only hard metric to say if the build is healthy or >> not. >> >> - We should not integrate anything until the build is green again... >> >> Also, we spent with Pablo a lot of time to have a green build in all >> platforms... I'd like to spend my time in other fun stuff than the CI :/ >> >> -- >> >> >> Guille Polito >> >> Research Engineer >> French National Center for Scientific Research - http://www.cnrs.fr[ >> http://www.cnrs.fr] >> >> >> Web: http://guillep.github.io[http://guillep.github.io] >> Phone: +33 06 52 70 66 13 >> >> > > > -- > > > > Guille Polito > > > Research Engineer > > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr> > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >

Sept. 11, 2017

Re: [Pharo-dev] argh, tests are failing!

by Guillermo Polito

On Mon, Sep 11, 2017 at 7:19 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi torsten > > From a process I think that we decided that external packages should > be managed like the following: > > - PR (from people) to change the code in Pharo > + issues a PR to Iceberg. > > - then Iceberg team merge PR + > issue a new PR for Pharo integration > > So I think that this is what you describe too? > Yes, that's what I described in ESUG too :) https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces… On the way back from ESUG we discussed with Esteban a way to support this kind of scenarios cleanly and without needing too much of a refactor ;) > > Like that we do not have deadlock and can always have a stable version. > > Stef > > > > > > > On Sun, Sep 10, 2017 at 7:16 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > > > to explain: > > > > we have lots of uncategorized methods and non commented classes. For > some time we had to accept this ugly situation that old and legacy code. > For Pharo 4 and 5 > > I invested a lot of time to clean this up right before the release date. > But with 6.0 such a round was not done and in 6.0 and 6.1 it looks like a > mess again. > > > > Why? Because we introduced new features and code and never defined a > certain level of quality for code we include. But our initial goal with > Pharo was (and > > hopefully still is) to cleanup things up and do better than before. > > > > So we should not forget about quality and so I spend some time last on > this again - now for Pharo 7. For instance #setUp and #tearDown in SUnit > should be > > in "running" as it was defined for TestCase subclasses. Also #hash and > #= should be in "comparing" protocol. Also the goal is coming back to an > image where > > all methods are categorized and where all classes have a comment. > > > > But for me it absolutely makes no sense to reinvest the time over and > over into the same cleanups while others can easily make a mess again. > > > > So we should RAISE THE QUALITY BAR to ensure that we keep with such a > quality level. Especially as see each build to be a release and the real > release once > > a year often is more or less a snapshot. > > > > So I also wrote a new test called "ProperMethodCategorizationTest" and > while cleaning up #hash it was green. So ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > > showed no problem and I committed and have sent a Pull request. This > looked like any other new contribution. > > > > What I did not knew at this time was that Iceberg code is not in git > repository - but managed externally. So while I fixed the code in my image > with wrongly categorized hash > > method in an Iceberg class (IceSemanticVersion) the system did not show > me that this change did not move to GitHub. > > > > Now I know - but this has such bad side effect when we do changes and > these packages are in the image - but not managed with the pharo repository. > > > > Long story short: one can not fix this situation with a simple PR as > Iceberg code is not under the "pharo" repo umbrella. > > > > I already submitted a PR for Iceberg > > > > https://github.com/pharo-vcs/iceberg/pull/458 > > > > and Esteban included that already - but only in Iceberg. We now need to > include Iceberg. > > > > Several lessons learned from my side: > > - doing changes and having green tests in the image is not enough > > - also doing a commit and PR does not mean all of your changes are on > GitHub > > - it is not a good situation when a part of the image code is managed > with "pharo" repository and another part is managed externally - I see this > as a problem of > > the new process we should discuss and address > > - we should nonetheless try to define tests to show the edges where we > can improve and cleanup (without a test it would not have been noticed that > while I did my best > > to cleanup the current way of managing Iceberg prevented my fix to > be into the image in the first place) > > > > I dont know what need to be done to include a new iceberg version or > when this will happen from Estebans side - but as soon as it is done this > test should be green again. > > > > Thanks > > T. > > > > > > Gesendet: Sonntag, 10. September 2017 um 18:24 Uhr > > Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> > > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Betreff: Re: [Pharo-dev] argh, tests are failing! > > > > Yes we know but have no idea how to recategorise Iceberg protocols > > > > On Sun, Sep 10, 2017 at 1:03 PM, Pavel Krivanek < > pavel.krivanek@gmail.com[mailto:pavel.krivanek@gmail.com]> wrote: > > > > Of course you are right, the Integrators should really take care on it. > > > > Before it were only common random failures but the main problem is with > this PR: > > https://github.com/pharo-project/pharo/pull/264[https:/ > /github.com/pharo-project/pharo/pull/264] > > > > The new test testHashMethodNeedsToBeInComparingProtocol fails on > classIceSemanticVersion > > > > -- Pavel > > > > > > 2017-09-10 10:13 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com[ > mailto:guillermopolito@gmail.com]>: > > Hi all, > > > > Since a couple of builds we have consistently failing the following > tests: > > > > > > GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2[ > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull% > 20request%20and%20branch%20Pipeline/job/development/ > 110/testReport/junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/ > testDeliverNow2/]GT.EventRecorder.Tests.Core.GTEventRecorderTest. > testNotDeliveredDataShouldBeResent[https://ci.inria.fr/ > pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/ > testNotDeliveredDataShouldBeResent/]Kernel.Tests.Processes.MutexTest. > testFailedCriticalSectionShouldUnblockWaitingOne[https://ci. > inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull% > 20request%20and%20branch%20Pipeline/job/development/ > 110/testReport/junit/Kernel.Tests.Processes/MutexTest/ > testFailedCriticalSectionShouldUnblockWaitingOne/] > ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_2/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_3/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_4/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_5/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_6/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_7/] > > > > > > Green builds are the only hard metric to say if the build is healthy or > not. > > > > - We should not integrate anything until the build is green again... > > > > Also, we spent with Pablo a lot of time to have a green build in all > platforms... I'd like to spend my time in other fun stuff than the CI :/ > > > > -- > > > > > > Guille Polito > > > > Research Engineer > > French National Center for Scientific Research - http://www.cnrs.fr[ > http://www.cnrs.fr] > > > > > > Web: http://guillep.github.io[http://guillep.github.io] > > Phone: +33 06 52 70 66 13 > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 11, 2017

Re: [Pharo-dev] argh, tests are failing!

by Guillermo Polito

Thanks Denis On Mon, Sep 11, 2017 at 11:35 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I will take a look into Mutex > > 2017-09-10 10:13 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Hi all, >> >> Since a couple of builds we have consistently failing the following tests: >> >> >> - GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2 >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - GT.EventRecorder.Tests.Core.GTEventRecorderTest.testNotDeliv >> eredDataShouldBeResent >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - Kernel.Tests.Processes.MutexTest.testFailedCriticalSectionSh >> ouldUnblockWaitingOne >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> - ReleaseTests.Categorization.ProperMethodCategorizationTest.t >> estHashMethodNeedsToBeInComparingProtocol >> <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> >> >> >> >> Green builds are the only hard metric to say if the build is healthy or >> not. >> >> - We should not integrate anything until the build is green again... >> >> Also, we spent with Pablo a lot of time to have a green build in all >> platforms... I'd like to spend my time in other fun stuff than the CI :/ >> >> -- >> >> >> >> Guille Polito >> >> >> Research Engineer >> >> French National Center for Scientific Research - *http://www.cnrs.fr* >> <http://www.cnrs.fr> >> >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 11, 2017

Re: [Pharo-dev] argh, tests are failing!

by Guillermo Polito

On Sun, Sep 10, 2017 at 7:16 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > to explain: > > we have lots of uncategorized methods and non commented classes. For some > time we had to accept this ugly situation that old and legacy code. For > Pharo 4 and 5 > I invested a lot of time to clean this up right before the release date. > But with 6.0 such a round was not done and in 6.0 and 6.1 it looks like a > mess again. > > Why? Because we introduced new features and code and never defined a > certain level of quality for code we include. But our initial goal with > Pharo was (and > hopefully still is) to cleanup things up and do better than before. > > So we should not forget about quality and so I spend some time last on > this again - now for Pharo 7. For instance #setUp and #tearDown in SUnit > should be > in "running" as it was defined for TestCase subclasses. Also #hash and #= > should be in "comparing" protocol. Also the goal is coming back to an image > where > all methods are categorized and where all classes have a comment. > > But for me it absolutely makes no sense to reinvest the time over and over > into the same cleanups while others can easily make a mess again. > > So we should RAISE THE QUALITY BAR to ensure that we keep with such a > quality level. Especially as see each build to be a release and the real > release once > a year often is more or less a snapshot. > > So I also wrote a new test called "ProperMethodCategorizationTest" and > while cleaning up #hash it was green. So ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > showed no problem and I committed and have sent a Pull request. This > looked like any other new contribution. > Yes yes, I can't agree more. We need to add Lint rules running by default also. > > What I did not knew at this time was that Iceberg code is not in git > repository - but managed externally. So while I fixed the code in my image > with wrongly categorized hash > method in an Iceberg class (IceSemanticVersion) the system did not show me > that this change did not move to GitHub. > Now I know - but this has such bad side effect when we do changes and > these packages are in the image - but not managed with the pharo repository. > Yep, this should be fixed as soon as we have multiple subdirectories/subprojects in iceberg. As soon as that is supported we will probably move iceberg to a subtree structure as explained in here: https://www.slideshare.net/GuillePolito1/understanding-the-pharo-dev-proces… https://github.com/guillep/PharoIntegrationProcess/wiki/Analysis-of-sub-pro… > > Long story short: one can not fix this situation with a simple PR as > Iceberg code is not under the "pharo" repo umbrella. > > I already submitted a PR for Iceberg > > https://github.com/pharo-vcs/iceberg/pull/458 > > and Esteban included that already - but only in Iceberg. We now need to > include Iceberg. > > Several lessons learned from my side: > - doing changes and having green tests in the image is not enough > - also doing a commit and PR does not mean all of your changes are on > GitHub > - it is not a good situation when a part of the image code is managed > with "pharo" repository and another part is managed externally - I see this > as a problem of > the new process we should discuss and address > - we should nonetheless try to define tests to show the edges where we > can improve and cleanup (without a test it would not have been noticed that > while I did my best > to cleanup the current way of managing Iceberg prevented my fix to be > into the image in the first place) > While the test is an improvement over the current situation, I ask myself if this particular validation of the protocols shouldn't be a Renraku rule. > > I dont know what need to be done to include a new iceberg version or when > this will happen from Estebans side - but as soon as it is done this test > should be green again. > As Pavel said, the iceberg version that is included in the system is the one described in BaselineOfIDE >> loadIceberg Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:v0.5.7'; load. (Smalltalk classNamed: #Iceberg) enableMetacelloIntegration: true. So updating that method with the new iceberg version and pushing that to Pharo should be enough. In any case, my mail was there just to raise the issue of the failing tests. We should care about failing tests, and I'll cry out loud everytime they are broken, just to make it explicit. > Thanks > T. > > > Gesendet: Sonntag, 10. September 2017 um 18:24 Uhr > Von: "Stephane Ducasse" <stepharo.self(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] argh, tests are failing! > > Yes we know but have no idea how to recategorise Iceberg protocols > > On Sun, Sep 10, 2017 at 1:03 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com[ > mailto:pavel.krivanek@gmail.com]> wrote: > > Of course you are right, the Integrators should really take care on it. > > Before it were only common random failures but the main problem is with > this PR: > https://github.com/pharo-project/pharo/pull/264[https:/ > /github.com/pharo-project/pharo/pull/264] > > The new test testHashMethodNeedsToBeInComparingProtocol fails on > classIceSemanticVersion > > -- Pavel > > > 2017-09-10 10:13 GMT+02:00 Guillermo Polito <guillermopolito(a)gmail.com[ > mailto:guillermopolito@gmail.com]>: > Hi all, > > Since a couple of builds we have consistently failing the following tests: > > > GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2[ > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull% > 20request%20and%20branch%20Pipeline/job/development/ > 110/testReport/junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/ > testDeliverNow2/]GT.EventRecorder.Tests.Core.GTEventRecorderTest. > testNotDeliveredDataShouldBeResent[https://ci.inria.fr/ > pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/GT.EventRecorder.Tests.Core/GTEventRecorderTest/ > testNotDeliveredDataShouldBeResent/]Kernel.Tests.Processes.MutexTest. > testFailedCriticalSectionShouldUnblockWaitingOne[https://ci. > inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull% > 20request%20and%20branch%20Pipeline/job/development/ > 110/testReport/junit/Kernel.Tests.Processes/MutexTest/ > testFailedCriticalSectionShouldUnblockWaitingOne/] > ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_2/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_3/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_4/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_5/]ReleaseTests.Categorization. > ProperMethodCategorizationTest.testHashMethodNeedsToBeInCompa > ringProtocol[https://ci.inria.fr/pharo-ci-jenkins2/job/Test% > 20pending%20pull%20request%20and%20branch%20Pipeline/job/ > development/110/testReport/junit/ReleaseTests.Categorization/ > ProperMethodCategorizationTest/testHashMethodNeedsToBeInCompa > ringProtocol_6/]ReleaseTests.Categorization.ProperMethodCategorizationTest > .testHashMethodNeedsToBeInComparingProtocol[https://ci.inria. > fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request% > 20and%20branch%20Pipeline/job/development/110/testReport/ > junit/ReleaseTests.Categorization/ProperMethodCategorizationTest/ > testHashMethodNeedsToBeInComparingProtocol_7/] > > > Green builds are the only hard metric to say if the build is healthy or > not. > > - We should not integrate anything until the build is green again... > > Also, we spent with Pablo a lot of time to have a green build in all > platforms... I'd like to spend my time in other fun stuff than the CI :/ > > -- > > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr[ > http://www.cnrs.fr] > > > Web: http://guillep.github.io[http://guillep.github.io] > Phone: +33 06 52 70 66 13 > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 11, 2017

Re: [Pharo-dev] Can Realm (DB) and Pharo play together (or can we have a Pharo Realm Object Server to ROS) ?

by Serge Stinckwich

Hi Cedrick, If you want to develop mobile app, you should discuss with Noury and have a look to Pharo/JS: https://pharojs.github.io/ âCan you move such discussions on pharo-users mailing-list and not pharo-dev ? Thank you.â On Sun, Sep 10, 2017 at 12:14 PM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Hello all, > > Iâve spent some time in the summer in what I call my quest to the ultimate > and easy and fun architecture to prototype some personal administration > apps and have fun :-) > Iâll share some experience and wonder if there are alternative in Pharo. > > I want app that are mobile firsts, then manageable with a computer (for > more complex administrative tasks). > I want them reactive (I especially like reactive data driven application > like meteor.js), ubiquitous around my devices and not always connected > (offline-first - this is very important if not the first objective). > > Ok, so I was lurking around looking for server and mobile distributed > databases and I finally found Realm (https://realm.io/products/ > realm-mobile-platform/) which is a cool architecture plenty of promises, > well documented, lots of tutorials... The architecture is composed of 2 > products: > - Realm DB [1] that runs on mobile device - multiplatform - fully > open-source - performant - an object DB with some limitation though > - Realm Object Server (ROS) [2] - provide two-way data sync simple and > easy - BUT proprietary even if free for developers â¦ the entry point for > serious developments (in particular access programmatically to the server) > is very expensive ! 1500$mo ! > > The developer edition with is free is already quite outstanding to me. > Looks at this demo page on GitHub [3] ! > > Butâ¦ without any control to the ROS, I find ROS quite limited finally. I > may then use the DB part, ROS free for what really need sync reactivity > between devices or between group of people (like a black board), but store > all less transient information to WhateverNoSQLDB probably in REST. > > Anyway I want to share that with you because it rings a smalltalk bell in > my headâ¦ itâs about object data, live feeling, and I want to use Pharo on > the server :) > > Maybe some people here have thought of an alternative ROS in Pharo or > Gemstone ? Any ideas or remarks ? > I was aware of sebastian Flow living full-stack framework attempt but > donât know more. > > TIA > CÃ©drick > > NB: Pharo looks more and more great ! Congratulations guys for you job ! I > hope ESUG was nice. > Iâve just tried Telepharo on Pharo 6 (64 bit). Really great work too... It > works like a charm, out of the box on low cost dedicated ubuntu servers [4] > => 10â¬mo > Pharo 64 tinyBenchmarks is 2,75 times slower than on my Mac mini Core i5 > 2,5GHz from 2012 with SSD (I guess itâs not that bad and usable for > personal applications servers). I think itâ about 3 times faster than on a > raspberry Pi. > Mac mini (32 bit version): '1329870129 bytecodes/sec; 108576799 sends/secâ > Dedibox Low Cost server (64 bit version)â '595695171 bytecodes/sec; > 39441333 sends/sec' > > NB2: to download/install Pharo from command line, on the web site > instructions, it seems it lacks the trailing slash. I had to add it. > > curl get.pharo.org/64*/* | bash > > > [1] https://realm.io/products/realm-mobile-database/ > [2] https://realm.io/products/realm-mobile-platform/ > [3] https://github.com/realm-demos > [4] https://www.online.net/fr/serveur-dedie/dedibox-sc > > > -- Serge Stinckwich UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Sept. 11, 2017

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

by Denis Kudriashov

Anybody else? 2017-08-31 10:29 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > > > 2017-08-31 10:24 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Hi. >> >> We now have very generic message names: >> - pin >> - unpin >> - setPinned: >> - isPinned >> >> Problem that they collide with possible domain related names. >> For example I implemented pinning of tabs in Calypso and I found that I >> overrides #pin and #isPinned messages. Then I fix it with different names. >> Probably menus also uses pin word but without overrides >> >> What you think about renaming pinning messages? Something like: >> - pinMemory >> > > I would use pinInMemory > > -- Pavel > > >> - unpinMemory >> - isMemoryPinned >> - setPinnedMemory: >> - pinMemoryDuring: (if we will introduce it) >> >> I think it is easy to do now because not much code uses pinning >> > >

Sept. 11, 2017

Re: [Pharo-dev] argh, tests are failing!

by Guillermo Polito

Hi Juraj, think that it may really depend on the machine and the state of the system. Slower slave machines could not really work with that timeout... The question is how could we make such test more robust. On Sun, Sep 10, 2017 at 6:41 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Hi, > > I have checked the EventRecorderTests and it works on my computer. The > only reason that it might not work on other cases is that there an assert > for 'semaphore waitTimeoutMSecs: 200â. I can put higher timeout if > necessary. The timeout 200 has worked for couple of years, right?. There > might be another issue. > > Cheers, > Juraj > > El 10-09-2017, a las 10:13, Guillermo Polito <guillermopolito(a)gmail.com> > escribiÃ³: > > Hi all, > > Since a couple of builds we have consistently failing the following tests: > > > - GT.EventRecorder.Tests.Core.GTEventRecorderTest.testDeliverNow2 > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - GT.EventRecorder.Tests.Core.GTEventRecorderTest. > testNotDeliveredDataShouldBeResent > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - Kernel.Tests.Processes.MutexTest.testFailedCriticalSectionShoul > dUnblockWaitingOne > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > - ReleaseTests.Categorization.ProperMethodCategorizationTest. > testHashMethodNeedsToBeInComparingProtocol > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> > > > > Green builds are the only hard metric to say if the build is healthy or > not. > > - We should not integrate anything until the build is green again... > > Also, we spent with Pablo a lot of time to have a green build in all > platforms... I'd like to spend my time in other fun stuff than the CI :/ > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - *http://www.cnrs.fr* > <http://www.cnrs.fr/> > > > *Web:* *http://guillep.github.io* <http://guillep.github.io/> > *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 11, 2017

Re: [Pharo-dev] poor state of fuel

by Norbert Hartl

> Am 11.09.2017 um 09:35 schrieb H. Hirzel <hannes.hirzel(a)gmail.com>: > >> On 9/10/17, Norbert Hartl <norbert(a)hartl.name> wrote: >> Max, >> >> Just an update. Martin commited a new package that solves the >> encoding/decoding of SmallInteger and Character. Together with the patch >> from nicolas my dumps work again >> >> Norbert > > You mean you managed to export Fuel objects in Pharo 4 and import them > in Pharo 6.1? > No, written in 6.1 64 bit and read in 6.1 bit 64 bit. Norbert > --Hannes > > >>> Am 29.08.2017 um 21:42 schrieb Max Leske <maxleske(a)gmail.com>: >>> >>> Thanks Tim. >>> >>> Norbert, I just saw that I have already created an issue for the 64-bit >>> problems. I donât know whether tackling that will help you though. In any >>> case, Iâll see that we try to work on those problems. >>> >>> I canât give you an exact timeline because I will be on holiday but I >>> guess I can make an integration by around mid September. >>> >>> Cheers, >>> Max >>> >>> >>> >>>> On 29 August 2017 at 16:09:06, Tim Mackinnon (tim(a)testit.works) wrote: >>>> >>>> As a small data point, a fuel file written out on AWS Lambda Linux (not >>>> sure what version - I think it's an ubuntu, but they don't really say), >>>> is readable on OS X 64bit . >>>> >>>> So it seems like you must have found something unusual. >>>> >>>> Tim >>>> >>>> Sent from my iPhone >>>> >>>>> On 29 Aug 2017, at 11:13, Max Leske <maxleske(a)gmail.com> wrote: >>>>> >>>>> Hi Norbert, >>>>> >>>>> We still maintain Fuel. >>>>> >>>>> I was not aware of the problem you describe. Could you open an issue on >>>>> github (https://github.com/theseion/Fuel/issues) with a detailed >>>>> explanation and, if possible, steps to reproduce the problem? >>>>> >>>>> Cheers, >>>>> Max >>>>> >>>>>> On 29 August 2017 at 11:04:34, Norbert Hartl (norbert(a)hartl.name) >>>>>> wrote: >>>>>> >>>>>> I'm migrating most of my projects to pharo 6.1 at the moment. I come >>>>>> from pharo 4, I skipped pharo 5. I use 64 bit which removes a lot of >>>>>> stuff that does not need to be installed and makes deployment better. >>>>>> That really feels much better. >>>>>> >>>>>> I use jenkins and there if a test fails a fuel dump is written to disk. >>>>>> The jenkins server is ubuntu linux with the vm of the opensuse build. >>>>>> My laptop has Mac OS and cannot read back those fuel dumps. I use the >>>>>> same image version on jenkins and my laptop. Both are 64bit. >>>>>> >>>>>> I asked that on discord and there was a mentioning that not only the 64 >>>>>> bit fuel has problems. So I wanted to ask what is the state of fuel >>>>>> right now. I consider fuel one of the core technologies in pharo and it >>>>>> is sad if it just stops working. >>>>>> >>>>>> Any feedback is highly appreciated, >>>>>> >>>>>> Norbert >>>>>> >>

Sept. 11, 2017

Re: [Pharo-dev] Iceberg causes 64 bit VM core dump on Ubuntu

by Alistair Grant

Hi Stef, On Mon, Sep 11, 2017 at 11:03:58AM +0200, stephan wrote: > On 10-09-17 11:23, Alistair Grant wrote: > >Iceberg enableMetacelloIntegration: true. > >Metacello new > > repository: 'github://akgrant43/FileAttributes/src'; > > baseline: 'FileAttributes'; > > load. > > Pharo-7.0.0-alpha.build.110.sha.5827735.arch.64bit > pharo-linux-x86_64threaded-201708312323-caa8241 > > Ubuntu 16.04LTS > > When loading: PrimitiveFailed: primitive #primFileMasks in > FileAttributesPluginPrims failed > > Stephan Thanks for taking a look at this. I realised that this was a bad example after I posted it. This script also demonstrates the problem: | pharoRepository | Iceberg enableMetacelloIntegration: true. Metacello new repository: 'github://akgrant43/pharo-akgosprocess/mc'; baseline: 'AKGOSProcess'; load. pharoRepository := IceRepository registry detect: [ :each | each name = 'pharo-akgosprocess' ]. pharoRepository pull. Less manual steps :-) Thanks again, Alistair

Sept. 11, 2017

Re: [Pharo-dev] Can Realm (DB) and Pharo play together (or can we have a Pharo Realm Object Server to ROS) ?

by CÃ©drick BÃ©ler

Hi Todd, > I do a lot of iOS development. I've looked at Realm. I don't trust it. I do like Sqlite. I have written the following frameworks for iOS. > > https://github.com/tblanchard/objectivefmdb <https://github.com/tblanchard/objectivefmdb> > > I use it constantly on iOS development. I would like to port it to Pharo, possibly with GLORP front end. > > I have an equivalent library written in PHP (I like PHP for server work) that works against a PostgreSQL database. > > I use this a lot to field iOS apps with server back ends very quickly. I'm happy to share it all. Thanks for sharing. I definitely will have a look soon. > > But I think trying to get Realm, a proprietary data store to work well with Pharo something of a waste of time due to the proprietary nature of it. Just to be sure, If I understand well, the realm data store (on mobiles devices) is fully open source (Apache 2.0). I think it was not the case at start in 2014 but it is now. They are seen as an alternative to SQLite. https://github.com/realm <https://github.com/realm> This is the other component of the architecture that is closed source (the realm object server). > > I am happy to help you out though - I've written a LOT of persistence active record type things and am pretty dang handy with GLORP as well. > > Drop me a note if you want to collaborate. Thanks for the proposition, See you soon CÃ©drick > > -Todd Blanchard > tblanchard(a)mac.com <mailto:tblanchard@mac.com> > > >> On Sep 10, 2017, at 3:14 AM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com <mailto:cdrick65@gmail.com>> wrote: >> >> Hello all, >> >> Iâve spent some time in the summer in what I call my quest to the ultimate and easy and fun architecture to prototype some personal administration apps and have fun :-) >> Iâll share some experience and wonder if there are alternative in Pharo. >> >> I want app that are mobile firsts, then manageable with a computer (for more complex administrative tasks). >> I want them reactive (I especially like reactive data driven application like meteor.js), ubiquitous around my devices and not always connected (offline-first - this is very important if not the first objective). >> >> Ok, so I was lurking around looking for server and mobile distributed databases and I finally found Realm (https://realm.io/products/realm-mobile-platform/ <https://realm.io/products/realm-mobile-platform/>) which is a cool architecture plenty of promises, well documented, lots of tutorials... The architecture is composed of 2 products: >> - Realm DB [1] that runs on mobile device - multiplatform - fully open-source - performant - an object DB with some limitation though >> - Realm Object Server (ROS) [2] - provide two-way data sync simple and easy - BUT proprietary even if free for developers â¦ the entry point for serious developments (in particular access programmatically to the server) is very expensive ! 1500$mo ! >> >> The developer edition with is free is already quite outstanding to me. Looks at this demo page on GitHub [3] ! >> >> Butâ¦ without any control to the ROS, I find ROS quite limited finally. I may then use the DB part, ROS free for what really need sync reactivity between devices or between group of people (like a black board), but store all less transient information to WhateverNoSQLDB probably in REST. >> >> Anyway I want to share that with you because it rings a smalltalk bell in my headâ¦ itâs about object data, live feeling, and I want to use Pharo on the server :) >> >> Maybe some people here have thought of an alternative ROS in Pharo or Gemstone ? Any ideas or remarks ? >> I was aware of sebastian Flow living full-stack framework attempt but donât know more. >> >> TIA >> CÃ©drick >> >> NB: Pharo looks more and more great ! Congratulations guys for you job ! I hope ESUG was nice. >> Iâve just tried Telepharo on Pharo 6 (64 bit). Really great work too... It works like a charm, out of the box on low cost dedicated ubuntu servers [4] => 10â¬mo >> Pharo 64 tinyBenchmarks is 2,75 times slower than on my Mac mini Core i5 2,5GHz from 2012 with SSD (I guess itâs not that bad and usable for personal applications servers). I think itâ about 3 times faster than on a raspberry Pi. >> Mac mini (32 bit version): '1329870129 bytecodes/sec; 108576799 sends/secâ >> Dedibox Low Cost server (64 bit version)â '595695171 bytecodes/sec; 39441333 sends/sec' >> >> NB2: to download/install Pharo from command line, on the web site instructions, it seems it lacks the trailing slash. I had to add it. >> curl get.pharo.org/64 <http://get.pharo.org/64>/ | bash >> >> [1] https://realm.io/products/realm-mobile-database/ <https://realm.io/products/realm-mobile-database/> >> [2] https://realm.io/products/realm-mobile-platform/ <https://realm.io/products/realm-mobile-platform/> >> [3] https://github.com/realm-demos <https://github.com/realm-demos> >> [4] https://www.online.net/fr/serveur-dedie/dedibox-sc <https://www.online.net/fr/serveur-dedie/dedibox-sc> >> >> >

Sept. 11, 2017