Dec. 20, 2017
9:51 a.m.
On 12/20/2017 10:48 AM, Thierry Goubier wrote:
Hi Cyril,
as said before, those are solved by using a more recent vm, such as the 201710221351 linux 64bits vm. You're using an older one in the CI (the 201707201942), and, unless they have been updated, both stable and latest pharo vms as provided by pharo.org <http://pharo.org> are subjected to the segfault.
Ok, so we just need to wait for a new vm to be marked as stable? :) Thank you!
Regards,
Thierry
-- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France