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

Bintray and files.pharo.org update not working?

by Alistair Grant

Hi Everyone, It looks like: - Bintray is not being updated, nothing has appeared in the last 4 days at https://bintray.com/opensmalltalk/vm/cog/ - files.pharo.org isn't being updated properly, e.g. http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… has only 7 files in it. The Travis CI job for this commit succeeded: https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/352271097 Thanks, Alistair

March 12, 2018

FORGET WHAT I SAID: THERE ARE NOT NEW STABLES

by Esteban Lorenzano

because new stables were not stable :) Esteban

March 12, 2018

Re: [Pharo-dev] [ANN] New stable VMs promoted for both 7.0a and 6.1

by Esteban Lorenzano

meh :/ I restored the old stable VMs honestly, this thing of not having a stable and development branch on VM sucks. Esteban > On 12 Mar 2018, at 14:05, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On 12 March 2018 at 13:33, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi, >> >> as the subject said, I promoted new VMs from last week latests on both version 6.1 and 7.0a. >> this should fix some ongoing problems with versioning. >> >> please let me know if something is not working as expected. >> >> cheers! >> Esteban >> >> ps: I donât know what Iâm thinking aboutâ¦ of course you will let me know if something is not working as expected! ;) > > Maybe the jenkins build process... :-) > > .finished baselineInconsistency detected by ld.so: dl-close.c: 811: > _dl_close: Assertion `map->l_init_called' failed! > > Tobias hopes he's fixed it in 802de0a1b, but I haven't tested it yet. > The travis build for it should finish in about 15 minutes. > > Cheers, > Alistair >

March 12, 2018

Re: [Pharo-dev] Loading configuration of spur

by Javier PimÃ¡s

On Mon, Mar 12, 2018 at 9:25 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hmm no idea. The best I can think about is that that VMMaker version is > old (Pharo5 is at least 2 years old) and there is probably a dependency > between VMMaker and the compiler (thus that BytecodeEncoder ref). IF > VMMaker is overriding some methods in BytecodeEncoder, then what is > happenning is that you're breaking the compiler (?). > sounds very much like what i'm seeing. > > In any case, again, that is not the official VMMaker repository but a > mirror. > should I use the one here? http://source.squeak.org/VMMaker Do you still use the one in github? Because if not I would recommend removing it as it is a bit misleading. > On Mon, Mar 12, 2018 at 11:53 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com > > wrote: > >> Oh I forgot to write down the actual error. There is a MNU for >> BytecodeEncoder class>>#isExtension: which seems to have been removed from >> the image. It is a bit different to typical doesNotUnderstand errors >> because it opens an emergency evaluator and leaves the image unusable. >> >> On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Hi, >>> >>> I'll Esteban answer better but I don't know if that VMMaker mirror is >>> up to date. >>> >>> Taking a look at the images/newImage.sh script, it is using Pharo5.0. >>> But I see no reason for it not working on latest versions. Probably some >>> patches are required... >>> >>> What is your error? >>> >>> >>> On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s < >>> elpochodelagente(a)gmail.com> wrote: >>> >>>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 >>>> image, is that supported? I have this snippet that doesn't work: >>>> >>>> Metacello new >>>> filetreeDirectory: '../VMMaker/mc'; >>>> baseline: 'Spur'; >>>> load >>>> >>>> where ../VMMaker/mc is a clone of the official pharo repo at github. >>>> >>>> Cheers, >>>> pocho >>>> >>>> -- >>>> Javier PimÃ¡s >>>> Ciudad de Buenos Aires >>>> >>> >>> >>> >>> -- >>> >>> >>> >>> Guille Polito >>> >>> Research Engineer >>> >>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>> >>> CRIStAL - UMR 9189 >>> >>> 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 <06%2052%2070%2066%2013> >>> >> >> >> >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > 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 <06%2052%2070%2066%2013> > -- Javier PimÃ¡s Ciudad de Buenos Aires

March 12, 2018

Re: [Pharo-dev] [ANN] New stable VMs promoted for both 7.0a and 6.1

by Alistair Grant

On 12 March 2018 at 13:33, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > as the subject said, I promoted new VMs from last week latests on both version 6.1 and 7.0a. > this should fix some ongoing problems with versioning. > > please let me know if something is not working as expected. > > cheers! > Esteban > > ps: I donât know what Iâm thinking aboutâ¦ of course you will let me know if something is not working as expected! ;) Maybe the jenkins build process... :-) .finished baselineInconsistency detected by ld.so: dl-close.c: 811: _dl_close: Assertion `map->l_init_called' failed! Tobias hopes he's fixed it in 802de0a1b, but I haven't tested it yet. The travis build for it should finish in about 15 minutes. Cheers, Alistair

March 12, 2018

[ANN] New stable VMs promoted for both 7.0a and 6.1

by Esteban Lorenzano

Hi, as the subject said, I promoted new VMs from last week latests on both version 6.1 and 7.0a. this should fix some ongoing problems with versioning. please let me know if something is not working as expected. cheers! Esteban ps: I donât know what Iâm thinking aboutâ¦ of course you will let me know if something is not working as expected! ;)

March 12, 2018

Re: [Pharo-dev] Loading configuration of spur

by Guillermo Polito

Hmm no idea. The best I can think about is that that VMMaker version is old (Pharo5 is at least 2 years old) and there is probably a dependency between VMMaker and the compiler (thus that BytecodeEncoder ref). IF VMMaker is overriding some methods in BytecodeEncoder, then what is happenning is that you're breaking the compiler (?). In any case, again, that is not the official VMMaker repository but a mirror. On Mon, Mar 12, 2018 at 11:53 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > Oh I forgot to write down the actual error. There is a MNU for > BytecodeEncoder class>>#isExtension: which seems to have been removed from > the image. It is a bit different to typical doesNotUnderstand errors > because it opens an emergency evaluator and leaves the image unusable. > > On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi, >> >> I'll Esteban answer better but I don't know if that VMMaker mirror is up >> to date. >> >> Taking a look at the images/newImage.sh script, it is using Pharo5.0. But >> I see no reason for it not working on latest versions. Probably some >> patches are required... >> >> What is your error? >> >> >> On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com >> > wrote: >> >>> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 >>> image, is that supported? I have this snippet that doesn't work: >>> >>> Metacello new >>> filetreeDirectory: '../VMMaker/mc'; >>> baseline: 'Spur'; >>> load >>> >>> where ../VMMaker/mc is a clone of the official pharo repo at github. >>> >>> Cheers, >>> pocho >>> >>> -- >>> Javier PimÃ¡s >>> Ciudad de Buenos Aires >>> >> >> >> >> -- >> >> >> >> Guille Polito >> >> Research Engineer >> >> Centre de Recherche en Informatique, Signal et Automatique de Lille >> >> CRIStAL - UMR 9189 >> >> 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 <06%2052%2070%2066%2013> >> > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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

March 12, 2018

Re: [Pharo-dev] Pharo 7.0 does not includes "Metacello support for GitFileTree metadata-less mode"

by Juraj Kubelka

Hi! thank you, it works! Juraj > El 27-02-2018, a las 20:19, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> escribiÃ³: > > Le 25/02/2018 Ã 23:07, Cyril Ferlicot D. a Ã©crit : >> Hi! >> >> This support is in this PR: >> >> https://github.com/pharo-project/pharo/pull/950 >> >> It was not added in Pharo 7 during the last sync but was in Pharo 6.1. >> >> I hope in the future we will depend on Metacello as a project during the >> bootstrap instead of having the sources directly in the Pharo >> repository. It will help but it needs work. >> > > > Hi! > > It is integrated. Can you check in the latest Pharo please? > > -- > Cyril Ferlicot > https://ferlicot.fr >

March 12, 2018

Re: [Pharo-dev] Loading configuration of spur

by Javier PimÃ¡s

Oh I forgot to write down the actual error. There is a MNU for BytecodeEncoder class>>#isExtension: which seems to have been removed from the image. It is a bit different to typical doesNotUnderstand errors because it opens an emergency evaluator and leaves the image unusable. On Mon, Mar 12, 2018 at 6:10 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi, > > I'll Esteban answer better but I don't know if that VMMaker mirror is up > to date. > > Taking a look at the images/newImage.sh script, it is using Pharo5.0. But > I see no reason for it not working on latest versions. Probably some > patches are required... > > What is your error? > > > On Sun, Mar 11, 2018 at 7:14 PM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> > wrote: > >> Ok, now I moved forward but cannot load vmmaker sources into a pharo 61 >> image, is that supported? I have this snippet that doesn't work: >> >> Metacello new >> filetreeDirectory: '../VMMaker/mc'; >> baseline: 'Spur'; >> load >> >> where ../VMMaker/mc is a clone of the official pharo repo at github. >> >> Cheers, >> pocho >> >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires >> > > > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > 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 <06%2052%2070%2066%2013> > -- Javier PimÃ¡s Ciudad de Buenos Aires

March 12, 2018

Re: [Pharo-dev] pharo64+git crash

by Esteban Lorenzano

I think I will declare new stables today. this is becoming a too confusing, and latest VMs are working fine, AFAIK ;) Esteban > On 11 Mar 2018, at 19:41, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 11/03/2018 Ã 18:09, Javier PimÃ¡s a Ã©crit : >> Didn't work. Tried also with vmT70 and vmI70 and neither did work. Sometimes they segfault, sometimes they hang using 100% cpu. I noticed that being for pharo7 those vms seemed pretty old (aug-2017), so I tried vmTLatest70 and that one finally worked. > > Oh :( Thank you for pointing that it worked with the latest 70 vm. > > I must admit that I'm using directly downloaded recent vms to avoid that same segfault and not the pharo.org <http://pharo.org/> VMs, but the process for setting them is a bit complex. So I hoped that the problem was solved with the Pharo 7 VMs, which are newer. > > Thierry > >> On Sun, Mar 11, 2018 at 6:31 AM, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com> <mailto:thierry.goubier@gmail.com <mailto:thierry.goubier@gmail.com>>> wrote: >> Hi Javier, >> can you try with a 64 bits Pharo 7 vm >> (http://get.pharo.org/64/vm70 <http://get.pharo.org/64/vm70>)? The Pharo 6 64bits vm used to have >> segfaults upon code loading. >> Regards, >> Thierry >> Le 10/03/2018 Ã 22:59, Javier PimÃ¡s a Ã©crit : >> Hi, I wonder if I'm doing something wrong or using a wrong version: >> I download a pharo image (spur64) from >> http://files.pharo.org/get-files/61/pharo64.zip <http://files.pharo.org/get-files/61/pharo64.zip> >> <http://files.pharo.org/get-files/61/pharo64.zip <http://files.pharo.org/get-files/61/pharo64.zip>> >> and a 64 bit vm from: >> get.pharo.org/64/vm61 <http://get.pharo.org/64/vm61> <http://get.pharo.org/64/vm61 <http://get.pharo.org/64/vm61>> >> <http://get.pharo.org/64/vm61> >> Then I try to load a git repo like this: >> ./pharo Pharo.image ../scripts/loadSqueakNOSVM.st >> where the script just says >> "Based on the same file from the pharo-vm project" >> Author useAuthor: 'LoadVMMaker' during: [ >> Metacello new >> baseline: #Nopsys; >> repository: 'github://nopsys/CogNOS/VM-src'; >> load ]. >> (Smalltalk saveAs: 'generator') >> ifFalse: [ Smalltalk snapshot: false andQuit: true ]. >> and it crashes with the log pasted below. I cannot even load the >> code, any clue? >> Cheers, >> Pocho >> ---- >> Fetched -> BaselineOfNopsys-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Loaded -> BaselineOfNopsys-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Loading baseline of BaselineOfNopsys... >> Fetched -> SqueakNOS-VM-GitHub.1520523060 --- >> git@github.com:nopsys/CogNOS.git[master] --- >> /CogNOS/image/pharo-local/iceberg/nopsys/CogNOS/VM-src (Libgit) >> Fetched -> BaselineOfSpur-EstebanLorenzano.4 --- >> filetree:///CogNOS/VMMaker/mc [:] --- filetree:///CogNOS/VMMaker/mc >> Segmentation fault Sat Mar 10 18:36:05 2018 >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo >> Pharo VM version: 5.0-201707201942 Thu Jul 20 20:40:54 UTC 2017 >> gcc 4.6.3 [Production Spur 64-bit VM] >> Built from: CoInterpreter VMMaker.oscog-eem.2254 uuid: >> 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 >> With: StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: >> 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 >> Revision: VM: 201707201942 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git>> $ Date: >> Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 >> https://github.com/OpenSmalltalk/opensmalltalk-vm.git <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> >> <https://github.com/OpenSmalltalk/opensmalltalk-vm.git> $ >> Build host: Linux >> testing-gce-74d10329-bbfd-42e5-8995-b0e3a68c73cb >> 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 >> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux >> plugin path: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942 >> [default: /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/] >> C stack backtrace & registers: >> rax 0x0c1c5f40 rbx 0x0c1c5dd0 rcx 0x0c1c5ff8 rdx 0x0c1c5e88 >> rdi 0x0c1c5ba8 rsi 0x0c1c5ba8 rbp 0x0c1c5d18 rsp 0x0c1c60b0 >> r8 0x0c1c55e8 r9 0x0c1c56a0 r10 0x0c1c5758 r11 0x0c1c5810 >> r12 0x0c1c58c8 r13 0x0c1c5980 r14 0x0c1c5a38 r15 0x0c1c5af0 >> rip 0x0c1c6168 >> *[0x7ffd0c1c6168] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41ccd1] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x41d05f] >> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11670)[0x7f5dc882f670] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x4403cc] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo(ceSendAborttonumArgs+0xd6)[0x45b826] >> /CogNOS/image/pharo-vm/lib/pharo/5.0-201707201942/pharo[0x45bda3] >> [0x1501223] >> [0x7ffdffffffff] >> Smalltalk stack dump: >> 0x7ffd0c1cbcc0 M MCWorkingCopy >> class>ancestorsFromArray:cache: 0x2b4a8a0: a(n) MCWorkingCopy class >> 0x19abee8 is not a context >> 0x1a24a80 is not a context >> 0x19abd78 is not a context >> 0x1a2c118 is not a context >> ... >> -- Javier PimÃ¡s >> Ciudad de Buenos Aires >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires

March 12, 2018