Here is the tail of the typical terminal output: ... warning: sage/rings/finite_rings/element_givaro.pyx:1105:39: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1120:50: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1138:39: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1156:50: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1178:39: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1201:50: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1218:39: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1235:50: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1252:39: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1285:35: local variable 'r' referenced before assignment warning: sage/rings/finite_rings/element_givaro.pyx:1286:59: local variable 'r' referenced before assignment Cythonizing sage/rings/finite_rings/element_ntl_gf2e.pyx Cythonizing sage/rings/finite_rings/element_pari_ffelt.pyx Cythonizing sage/rings/finite_rings/finite_field_base.pyx Cythonizing sage/rings/finite_rings/hom_finite_field.pyx Cythonizing sage/rings/finite_rings/hom_finite_field_givaro.pyx Cythonizing sage/rings/finite_rings/hom_prime_finite_field.pyx Cythonizing sage/rings/finite_rings/integer_mod.pyx Cythonizing sage/rings/finite_rings/residue_field.pyx Cythonizing sage/rings/fraction_field_FpT.pyx Cythonizing sage/rings/fraction_field_element.pyx Cythonizing sage/rings/function_field/function_field_element.pyx Cythonizing sage/rings/integer.pyx Cythonizing sage/rings/integer_ring.pyx Cythonizing sage/rings/laurent_series_ring_element.pyx Cythonizing sage/rings/morphism.pyx Cythonizing sage/rings/noncommutative_ideals.pyx Cythonizing sage/rings/number_field/number_field_base.pyx Cythonizing sage/rings/number_field/number_field_element.pyx Cythonizing sage/rings/number_field/number_field_element_quadratic.pyx Cythonizing sage/rings/number_field/number_field_morphisms.pyx Cythonizing sage/rings/number_field/totallyreal.pyx ^Cmake: *** [build] Interrupt
real 813m6.056s user 206m52.660s sys 14m28.150s As we see, the system was doing mostly nothing. 2GB RAM and half of 2.6GB swap were filled at the time of interruption, load ~10, CPU wait ~95%. I'll keep all logs for a while, but I imagine they are unlikely to have anything unusual - things were going fine except for speed due to swap. It is a single core single thread 64-bit CPU (Athlon 64M), suggestions to use USB 3/PCIe SSD are funny but miss the point: for no apparent gain systems that were capable of building Sage can't do it anymore (or require tweaking to reduce parallelism). I find it quite worrisome since the situation may continue to worsen if not fixed. Unfortunately, I personally can't do much as I have no clue what is going on and how to debug it. What has changed in the new Cython that it requires so much memory??? Thank you, Andrey -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
