- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] VMs build process restored

by Cyril Ferlicot

On Thu, Feb 8, 2018 at 4:29 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Cyril, > Hi :) > > Why do you need to back port? Why can't you use the 7.x VM with 6.x images? The VM is intended to be backwards compatible. > For each Pharo release, Pharo defines stable vms. For example, in a Jenkins bash script if we execute this: wget -O- https://get.pharo.org/64/61+vm | bash It will download a fresh Pharo 6.1 image, a source file and a vm of the right OS marked as stable for Pharo 6.1. With this, we ensure that a certain Pharo release will not have a different vm too often because if changes are intended to be backwards compatible, there is always the possibility a problem get through (for example one time OSProcess stopped to work on OSX because of a problem with the system version). So, I *can* use the vm for Pharo 7 if I get it myself but through hacks in our scripts instead of using official distribution ways of Pharo. I would prefer to only use official distribution ways in order to reduce the complexity of our scripts. In conclusion what I mean by "backport" is that Pharo officially marks the current vm as stable for Pharo 6.1 to get it via zeroconf. -- Cyril Ferlicot https://ferlicot.fr

Feb. 8, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Sven Van Caekenberghe

> On 8 Feb 2018, at 13:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 7 Feb 2018, at 11:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> I made notes and will add a page with all the infos later today. (for http://pharo.org/contribute ) >> > > I added a simple page as a first step: > > http://pharo.org/review-fix > > > Marcus Already quite good, thank you.

Feb. 8, 2018

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

by Sven Van Caekenberghe

Starting/restarting with a running server in the image works OK for me (macOS) and recent Pharo 7. What is different for you ? > On 8 Feb 2018, at 12:51, Maximiliano Tabacman via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Maximiliano Tabacman <mtabacman(a)yahoo.com> > Subject: Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ? > Date: 8 February 2018 at 12:51:15 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Up until Pharo build 382 (sha 115e95c) you could load Seaside by using: > Metacello new > > > baseline:'Seaside3' > ; > > repository: 'github://SeasideSt/Seaside:master/repository' > ; > load > > If you adapt the baselineOf to include Pharo 7.x > > BUT, from build 383 onwards, and tested again just now with 509 (sha 1276a3f) the following happens: > - Download Pharo -- OK > - Load Seaside master -- OK > - Save and quit image -- OK > - Start image again -- Hangs and never completes starting > > In Ubuntu, this manifests as the main Pharo window opening, but never displaying anything inside it. > In Windows, the VM starts and closes without any warning, and no logs are created. > > I have no idea why this is happening, and I am not sure if the tests in Travis cover this scenario. > On Wednesday, February 7, 2018, 4:14:24 PM GMT-3, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > Thanks for pushing this. > I plan to work on migrating the seaside book to pillar when I'm done > with the moose book and the magritte booklet. > > Stef > > On Wed, Feb 7, 2018 at 1:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > > > Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems. > > > > Metacello new > > baseline:'Seaside3'; > > repository: 'github://SeasideSt/Seaside:master/repository'; > > load. > > > > Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ? > > > > This is _really_ important to make progress, IMHO. > > > > I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine. > > > > Sven > > > >> On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> > >> OK, Max, thanks for the reply. > >> > >> I will ask on the Pharo ML as well. > >> > >> I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. > >> > >>> On 6 Nov 2017, at 09:40, Max Leske <maxleske(a)gmail.com> wrote: > >>> > >>> Hi Sven, > >>> > >>> We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend. > >>> > >>> How urgent is the situation for you? > >>> > >>> Cheers, > >>> Max > >>> > >>> > >>> On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: > >>> > >>>> Hi, > >>>> > >>>> I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: > >>>> > >>>> project: 'Bootstrap' with: [ > >>>> spec > >>>> className: 'ConfigurationOfBootstrap'; > >>>> repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; > >>>> versionString: #stable ] > >>>> > >>>> I also tried the following: > >>>> > >>>> Metacello new > >>>> baseline:'Seaside3'; > >>>> repository: 'github://SeasideSt/Seaside:master/repository'; > >>>> load. > >>>> > >>>> What is the right/recommended way to do it ? > >>>> > >>>> Thx, > >>>> > >>>> Sven > >>>> > >>>> _______________________________________________ > >>>> seaside-dev mailing list > >>>> seaside-dev(a)lists.squeakfoundation.org > >>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > >>> _______________________________________________ > >>> seaside-dev mailing list > >>> seaside-dev(a)lists.squeakfoundation.org > >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > >> > > > > > >

Feb. 8, 2018

Re: [Pharo-dev] VMs build process restored

by Eliot Miranda

Hi Cyril, > On Feb 8, 2018, at 2:49 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > >> On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> (it was broken since december) >> >> Which means latest vm versions are latest builds from OSVM: >> >> 64bit >> >> â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip >> 32bit >> >> â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip >> >> Hints >> >> â¢ MacOS VMs now are signed! This should fix a lot of problems we had before. >> â¢ Please take note that win64 build lacks all library dependencies, and many things will not work (working on that). >> Thanks to Fabio to help me put all the pieces together. >> >> > ) > cheers, >> Esteban > > Hi! > > Just a little feedback. > > Currently, at Synectique, we added Pharo 61 64bits build to our > Jenkins. Those builds failed **a lot** because of segmentation faults. > We added a mechanism to retry two times when there was a segfault and > even like that we have failing builds. > > Since the restoration of the vms I removed the retry mechanism and I > added a hack to use the latest Pharo 70 vm > (http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead > of the stable pharo 61 vm. Since then, there was no crash due to the > VM. > This is a great improvement. > Then I have a question: Is it plan to release new stable 64bit vms for > Pharo 61? Currently, our builds are based on hacks and if no problem > is detected with the latest vm it would greatly help stability-wise to > have official vms that does not crash 3/5times when we load a project. > Also, I understand it can be hard to backport vms with the resources > of the community. :) Why do you need to back port? Why can't you use the 7.x VM with 6.x images? The VM is intended to be backwards compatible. > > -- > Cyril Ferlicot > https://ferlicot.fr >

Feb. 8, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #510: 21246-Store-main-window-title

by Marcus Denker

> On 8 Feb 2018, at 14:17, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #510 was: FAILURE. > > The Pull Request #809 was integrated: "21246-Store-main-window-title" > Pull request url: https://github.com/pharo-project/pharo/pull/809 > > Issue Url: https://pharo.fogbugz.com/f/cases/21246 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…> I see multiple times in the logs: [unix-32] Downloading the latest pharoVM: [unix-32] http://files.pharo.org/get-files/70/pharo-linux-stable.zip <http://files.pharo.org/get-files/70/pharo-linux-stable.zip> [unix-32] mkdir: cannot create directory âpharo-vmâ: File exists [kernel-unix-32] [branch_Pipeline_development-CMOUMEH7DVLJPL2EIJ6VPEHUQRS3W4AK3FD4ESTKJ3YGKZERQFUQ] Running shell script [Pipeline] [unix-32] echo [unix-32] Tests couldn't complete to run due to an exception I wonder if the mkdir is the problem? Even if not, it would be nice to get rid of the error... Marcus

Feb. 8, 2018

[Pharo 7.0-dev] Build #510: 21246-Store-main-window-title

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

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

Feb. 8, 2018

Re: [Pharo-dev] Reviewing Changes ?

by Marcus Denker

> On 7 Feb 2018, at 11:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > I made notes and will add a page with all the infos later today. (for http://pharo.org/contribute <http://pharo.org/contribute> ) > I added a simple page as a first step: http://pharo.org/review-fix <http://pharo.org/review-fix> Marcus

Feb. 8, 2018

Re: [Pharo-dev] VMs build process restored

by Esteban Lorenzano

> On 8 Feb 2018, at 11:49, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> (it was broken since december) >> >> Which means latest vm versions are latest builds from OSVM: >> >> 64bit >> >> â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip >> 32bit >> >> â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip >> â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip >> >> Hints >> >> â¢ MacOS VMs now are signed! This should fix a lot of problems we had before. >> â¢ Please take note that win64 build lacks all library dependencies, and many things will not work (working on that). >> Thanks to Fabio to help me put all the pieces together. >> >> > ) > cheers, >> Esteban > > Hi! > > Just a little feedback. > > Currently, at Synectique, we added Pharo 61 64bits build to our > Jenkins. Those builds failed **a lot** because of segmentation faults. > We added a mechanism to retry two times when there was a segfault and > even like that we have failing builds. > > Since the restoration of the vms I removed the retry mechanism and I > added a hack to use the latest Pharo 70 vm > (http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead > of the stable pharo 61 vm. Since then, there was no crash due to the > VM. > This is a great improvement. > Then I have a question: Is it plan to release new stable 64bit vms for > Pharo 61? yes :) > Currently, our builds are based on hacks and if no problem > is detected with the latest vm it would greatly help stability-wise to > have official vms that does not crash 3/5times when we load a project. > Also, I understand it can be hard to backport vms with the resources > of the community. :) > > -- > Cyril Ferlicot > https://ferlicot.fr >

Feb. 8, 2018

Re: [Pharo-dev] [Seaside-dev] How should I load Seaside/Bootstrap in Pharo 7 ?

by Maximiliano Tabacman

Up until Pharo build 382 (sha 115e95c) you could load Seaside by using:Metacello new baseline:'Seaside3'; repository: 'github://SeasideSt/Seaside:master/repository'; loadIf you adapt the baselineOf to include Pharo 7.x BUT, from build 383 onwards, and tested again just now withÂ 509 (sha 1276a3f) the following happens:- Download Pharo -- OK- Load Seaside master -- OK- Save and quit image -- OK- Start image again -- Hangs and never completes starting In Ubuntu, this manifests as the main Pharo window opening, but never displaying anything inside it.In Windows, the VM starts and closes without any warning, and no logs are created. I have no idea why this is happening, and I am not sure if the tests in Travis cover this scenario. On Wednesday, February 7, 2018, 4:14:24 PM GMT-3, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: Thanks for pushing this. I plan to work on migrating the seaside book to pillar when I'm done with the moose book and the magritte booklet. Stef On Wed, Feb 7, 2018 at 1:45 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Using [ https://github.com/SeasideSt/Seaside/pull/979 ] (I attach a manually modified BaselineOfSeaside3 that I used), I managed to load Seaside 3.2 (GitHub.1516790362) in Pharo 7 (Pharo-7.0+alpha.build.493.sha.d53a70bc946ed83b046f61ac35f00c67fa77269a (32 Bit)) and at least the load and some quick testing with ZnZincSeasideAdaptor (via the spec based Seaside Control Panel) seems to indicate no direct problems. > > Metacello new >Â baseline:'Seaside3'; >Â repository: 'github://SeasideSt/Seaside:master/repository'; >Â load. > > Why don't we integrate this so that others can load Seaside 3.2 in Pharo 7 too ? > > This is _really_ important to make progress, IMHO. > > I changed WABrowser>>#updateUrl: to send #name instead of #fullName to the selected class of the model. I am not sure that is entirely correct, but it seemed to work. Apart from that, the WAImageStatus web app worked fine. > > Sven > >> On 6 Nov 2017, at 09:49, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> OK, Max, thanks for the reply. >> >> I will ask on the Pharo ML as well. >> >> I think it is important that Seaside works on Pharo 7, it is an important use case and test during development, and very necessary as well. >> >>> On 6 Nov 2017, at 09:40, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Hi Sven, >>> >>> We don't have a build for Pharo 7 yet. Loading from github would be the recommended way. A quick look makes me think that it will require a bit of work to get the baseline set up correctly. I can't promise anything before next weekend. >>> >>> How urgent is the situation for you? >>> >>> Cheers, >>> Max >>> >>> >>> On 5 November 2017 at 19:22:03, Sven Van Caekenberghe (sven(a)stfx.eu) wrote: >>> >>>> Hi, >>>> >>>> I am stuck trying to move my main development to Pharo 7 because I have trouble loading Seaside (which I normally do indirectly by loading the Bootstrap project). Here is my dependency: >>>> >>>> project: 'Bootstrap' with: [ >>>> spec >>>> className: 'ConfigurationOfBootstrap'; >>>> repository: 'http://smalltalkhub.com/mc/TorstenBergmann/Bootstrap/main/'; >>>> versionString: #stable ] >>>> >>>> I also tried the following: >>>> >>>> Metacello new >>>> baseline:'Seaside3'; >>>> repository: 'github://SeasideSt/Seaside:master/repository'; >>>> load. >>>> >>>> What is the right/recommended way to do it ? >>>> >>>> Thx, >>>> >>>> Sven >>>> >>>> _______________________________________________ >>>> seaside-dev mailing list >>>> seaside-dev(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >>> _______________________________________________ >>> seaside-dev mailing list >>> seaside-dev(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev >> > >

Feb. 8, 2018

Re: [Pharo-dev] VMs build process restored

by Cyril Ferlicot

On Tue, Feb 6, 2018 at 5:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > (it was broken since december) > > Which means latest vm versions are latest builds from OSVM: > > 64bit > > â¢ http://files.pharo.org/get-files/70/pharo64-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux-threaded-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo64-win-latest.zip > 32bit > > â¢ http://files.pharo.org/get-files/70/pharo-linux-threaded-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-linux-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-mac-latest.zip > â¢ http://files.pharo.org/get-files/70/pharo-win-latest.zip > > Hints > > â¢ MacOS VMs now are signed! This should fix a lot of problems we had before. > â¢ Please take note that win64 build lacks all library dependencies, and many things will not work (working on that). > Thanks to Fabio to help me put all the pieces together. > > ) > cheers, > Esteban Hi! Just a little feedback. Currently, at Synectique, we added Pharo 61 64bits build to our Jenkins. Those builds failed **a lot** because of segmentation faults. We added a mechanism to retry two times when there was a segfault and even like that we have failing builds. Since the restoration of the vms I removed the retry mechanism and I added a hack to use the latest Pharo 70 vm (http://files.pharo.org/get-files/70/pharo64-linux-latest.zip) instead of the stable pharo 61 vm. Since then, there was no crash due to the VM. This is a great improvement. Then I have a question: Is it plan to release new stable 64bit vms for Pharo 61? Currently, our builds are based on hacks and if no problem is detected with the latest vm it would greatly help stability-wise to have official vms that does not crash 3/5times when we load a project. Also, I understand it can be hard to backport vms with the resources of the community. :) -- Cyril Ferlicot https://ferlicot.fr

Feb. 8, 2018