> Am 11.12.2024 um 15:19 schrieb Norbert Hartl <norb...@hartl.name>: > > > >> Am 05.12.2024 um 13:49 schrieb Guillermo Polito <guillermopol...@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
