erp5: XXX try to use recent gcc

stack/erp5/buildout.cfg

@@ -85,9 +85,9 @@ parts +=
   jupyter-notebook-initialized-scripts
 
 [gcc]
-# KumoFS is known not to build with gcc>6.
-# It may work with slightly more recent but not tested.
-part = gcc-5.5
+# XXX use recent gcc
+part = gcc-8.2
+
 
 # override instance-jupyter-notebook not to render into default template.cfg
 [instance-jupyter-notebook]

[Jérome Perrin]

I'm trying this on test performance

[Jérome Perrin]

@Tyagov I'm trying test performance with this, we'll see the result tomorrow

[Ivan Tyagov]

@jerome , I noticed testnode was busy with this :) BTW: your fix at least passes. Thanks FYI: I suspect that flaky tests gets affected by crontab's slapos commands (using CPU indirectly) ...

[Jérome Perrin]

Ah yes, good point about the crontab. I guess this is also an old slapos node where collect can take ages. I'm trying a bit more in this direction because I guess it can generally be nice if we can use more modern gcc here, but this might be hard. I already had to backport a fix for gtkmm that was not building with this gcc ( 12108256 )

[Jérome Perrin]

-> nexedi/slapos!756 (merged)