Hi all, I've rolled the stable version back to 10.3.1, please test.
@Norbert et al, we identified at least two issues: - a glibC incompatibility with Ubuntu 20.04 that arises because recently the build servers changed to a Debian, so all zeroconf users are impacted (except those using stable debian). - a vm crash that we are still investigating If you have the second issue, and you have a small reproducible case (like some small test set in your open source project) that we can use to reproduce the issue, that will accelerate our debugging process. Thanks all for understanding, G > Le 5 déc. 2024 à 10:45 AM, Norbert Hartl <norb...@hartl.name> a écrit : > > Thanks. > > And please tell us what data we can generate in order to help. It happened on > our CI and this is a place where I can introduce stuff which generates data > if it does not become too slow. > > Norbert > >> Am 05.12.2024 um 08:42 schrieb Guille Polito <guillermo.pol...@inria.fr>: >> >> Hi all, >> >> We had reports of issues observed with this version, we will rollback during >> the morning and after proceed to study the indicent. >> >> G >> >>> Le 4 déc. 2024 à 10:56 AM, Guille Polito <guillermo.pol...@inria.fr> a >>> écrit : >>> >>> Hi all, >>> >>> We’ve published a new VM release (v10.3.2) to be used with Pharo versions >>> 10 through 13. >>> Please check the change log here: >>> >>> https://github.com/pharo-project/pharo-vm/releases/tag/v10.3.2 >>> >>> The build is on the oven, new VMs should be available as soon as the build >>> farm finishes. >>> >>> Cheers, >>> G >>> _______________________________________________ >>> Pharo-vm mailing list -- pharo...@lists.pharo.org >>> To unsubscribe send an email to pharo-vm-le...@lists.pharo.org >> > > _______________________________________________ > Pharo-vm mailing list -- pharo...@lists.pharo.org > To unsubscribe send an email to pharo-vm-le...@lists.pharo.org
