December 2024 - Pharo-vm - lists.pharo.org

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi Norbert, the patch has not been merged yet. > > Are we talking about the same? > > the pharo-10 branch still has the issue The PR looks much better. But now I notice that with the compile and install options documented on github the vm in build/dist does not include some libraries, e.g, libcrypto.* libssl.* etc. How is the packaging done for the archives on files.pharo.org? thanks, Norbert > >> Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> >> >>> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >>> >>> >>> >>>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>>> >>>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>>> - run locally the failing tests >>>> >>>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>>> >>> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >>> >>> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >>> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >>> >> Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas >> >> Norbert >

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:51 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi Norbert, the patch has not been merged yet. > > Are we talking about the same? > > the pharo-10 branch still has the issue Ah right, I think I got so confused throughout the day that reading the PR made me think it has been merged already. Will try with the PR branch. Norbert > >> Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> >> >>> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >>> >>> >>> >>>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>>> >>>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>>> - run locally the failing tests >>>> >>>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>>> >>> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >>> >>> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >>> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >>> >> Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas >> >> Norbert >

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Guillermo Polito

Hi Norbert, the patch has not been merged yet. Are we talking about the same? the pharo-10 branch still has the issue > Le 11 dÃ©c. 2024 Ã 3:50â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > > >> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: >> >> >> >>> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >>> >>> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >>> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >>> - run locally the failing tests >>> >>> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >>> >> It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. >> >> In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. >> Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) >> > Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas > > Norbert

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norbert(a)hartl.name>: > > > >> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: >> >> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >> - run locally the failing tests >> >> This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. >> > It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. > > In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. > Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) > Running a vm from HEAD build let's it live longer but in the end it collapses as well. What is really wild now is that I cannot use the old binaries anymore. I have segfaults there, too. So I'm a bit out of ideas Norbert

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you > - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 > - run locally the failing tests > > This information could help us reduce the search space, and identify if itâs just the build environment or there is something else we have to deal with. > It seems you have figured it out. Since I started to compile my own vm I cannot build anything on my jenkins. In order to at least confirm a few things I've built a little infrastructure for me to generate vms in different combinations. I went down the rabbit hole and tried v10.21, v10.3.1 and v10.3.2 under debian 12 and all failed. Then I downgraded gcc to gcc-11 and retried. All are still failing. I read that the gcc 12 and gcc 11 more or less the same in that regard. Sadly it is not easy to go much back from where I am. I need to check on the jenkins and this is based on debian 12. So I could retry with older gccs but I'm not sure what will be the outcome. Right now I'm retrying with pharo-10 HEAD because your commit message sounded it is worth it (well, nothing else works) If you want me to test somethig please just say so. Norbert

Dec. 11, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 05.12.2024 um 14:26 schrieb Norbert Hartl <norbert(a)hartl.name>: > >> >> Also, anybody having a couple of minutes to test and help, if you see this issue locally, could you >> - build a VM (https://github.com/pharo-project/pharo-vm/) checking out tag v10.3.2 >> - run locally the failing tests > > I will take that for creating a vm build on my CI. a small update. I managed in 20 minutes to create a Dockerfile that seems to work: --- # # Dockerfile for building pharo-10 branch under ubuntu 22.04 # FROM ubuntu:22.04 RUN \ apt-get update && \ apt-get install -y wget curl unzip inetutils-ping gnupg libcurl3-gnutls && \ apt-get install -y \ build-essential \ cmake \ git \ python3-minimal \ pkg-config \ libgit2-dev \ libssh-dev \ libsdl2-dev \ libfreetype-dev \ libffi-dev && \ rm -rf /var/lib/apt/lists/* WORKDIR /opt RUN mkdir -p /opt/src WORKDIR /opt/src RUN git clone https://github.com/pharo-project/pharo-vm.git && cd pharo-vm && git checkout pharo-10 RUN cmake -S pharo-vm -B pharo-vm-build RUN cmake --build pharo-vm-build --target install RUN rm -rf pharo-vm-build/build/dist/pharo-vm RUN mv pharo-vm-build/build/dist /opt/pharo-vm RUN rm -rf pharo-vm-build pharo-vm --- Doing a docker build . in that directory builds the vm and installs it under /opt/pharo-vm/pharo In the end it copies the files to a special place. But this could also be a way to zip them and put them somewhere else. The most simple use would be to have a Dockerfile per combination OS-pharoVmVersion. Maybe this would work on github. If I find time I might try somethig along that line. That would make zeroconf survive and still we can support a bit more. Of course it duplicates some work on the OBS but that deals with much more to integrate in the system. For me two uses cases. What I do now is that the Dockerfile above builds and installs the vm in the docker image. I upload these and make them the basis of my docker builds so this is the closest I could get and apart from obstacles that might occur it works. Just in case some has interests in the Dockerfile or volunteering building a repo with those Dockerfiles. Norbert

Dec. 6, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by stephane ducasse

Thanks you for your time and energy fighting with this. This is really great to have you around. I hope that we will get out this situation with a nicer infrastructure. S > On 5 Dec 2024, at 14:04, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > >> Le 5 dÃ©c. 2024 Ã 1:49â¯PM, Guillermo Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> >>> Just to be sure. In that case it would be nice to have a way to download precisely 10.3.1 in order to stay safe and we have time to plan countermeasure. >> >> If you want to control what you download, right now the safest way is to go to files.pharo.org <http://files.pharo.org/>, more precisely to https://files.pharo.org/vm/pharo-spur64/, and look for your architecture. >> >> There you will find the archives with the binaries we built. >> Details about naming conventions are found here: https://github.com/pharo-project/pharo-vm/wiki/About-Build-and-Artifacts >> >> That file server stores both released artifacts and intermediate build results. >> The released artifact is the first artifact with the corresponding version tag (e.g., 10.3.1, 10.2.0). >> This is generally the oldest in timestime, but you can confirm with the tags on github. > > Also, we improved the artifact naming to include also: > - suffixes (alpha, RC, SNAPSHOT) > - the distance to the released tag in the format [+x] where x is the commits. > > https://github.com/pharo-project/pharo-vm/pull/870 > > We have tested this in the dev branch, Iâll backport this in the stable branch. > This will allow us to clearly identify the release commit (the one without the +x tag in the name). > > G > _______________________________________________ > Pharo-vm mailing list -- pharo-vm(a)lists.pharo.org > To unsubscribe send an email to pharo-vm-leave(a)lists.pharo.org StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Dec. 5, 2024

Re: [Pharo-dev] Re: New VM Release v10.3.2

by Jan VranÃ½

Hi, > > > > Overall this is quite unfortunate. I hope there will be a better > > solution then everyone has to build their own vms. I think I need > > to plan some time to do it. > > We understand, and believe me, itâs unfortunate for us too. > We are working on it and hope to have some news in the following > weeks. > > > Speaking of this, it is worse than having to build your own. I'd perfectly happy to do so if I could, but I do not know the secret sauce needed so and nobody seems to know either [1]. In this particular case, I managed in the end to compile it from generated C source [2]. Now I need to back-port some fixes but again, I do not know the secret sauce needed to build a VMMaker image. I'd be great to fix this too (if not already). Best, Jan [1]: https://lists.pharo.org/empathy/thread/M5IOYAHP2QZ2I33OL74JFSRYVUJJR7HI [2]: https://github.com/janvrany/pharo-vm/commit/feb4e8f02aecbac5505b390d8bafb10…

Dec. 5, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Guillermo Polito

> Le 5 dÃ©c. 2024 Ã 2:26â¯PM, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > >> you should have some procedure how to get data so we can help. And everyone complaining about instability is suspect to exactly follow that :) Haha, this is indeed a nice idea, itâs true we have a lot of this in our heads. Iâll come up with something.

Dec. 5, 2024

Re: [Pharo-dev] New VM Release v10.3.2

by Norbert Hartl

> Am 05.12.2024 um 14:04 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > > >> Le 5 dÃ©c. 2024 Ã 1:49â¯PM, Guillermo Polito <guillermopolito(a)gmail.com> a Ã©crit : >> >> >>> Just to be sure. In that case it would be nice to have a way to download precisely 10.3.1 in order to stay safe and we have time to plan countermeasure. >> >> If you want to control what you download, right now the safest way is to go to files.pharo.org <http://files.pharo.org/>, more precisely to https://files.pharo.org/vm/pharo-spur64/, and look for your architecture. >> >> There you will find the archives with the binaries we built. >> Details about naming conventions are found here: https://github.com/pharo-project/pharo-vm/wiki/About-Build-and-Artifacts >> >> That file server stores both released artifacts and intermediate build results. >> The released artifact is the first artifact with the corresponding version tag (e.g., 10.3.1, 10.2.0). >> This is generally the oldest in timestime, but you can confirm with the tags on github. > > Also, we improved the artifact naming to include also: > - suffixes (alpha, RC, SNAPSHOT) > - the distance to the released tag in the format [+x] where x is the commits. perfect. We use git describe | sed -e 's/\-\([0-9][0-9]*\)\-.*/.\1/' for that. > > https://github.com/pharo-project/pharo-vm/pull/870 > > We have tested this in the dev branch, Iâll backport this in the stable branch. > This will allow us to clearly identify the release commit (the one without the +x tag in the name). > super! Thank you for the good work!! Norbert > G

Dec. 5, 2024