I think it started with the openblas switch. If you want to collect some data then try to reproduce the hang, then attach gdb and print a backtrace.
On Saturday, March 18, 2017 at 8:56:21 AM UTC+1, Simon King wrote: > > On 2017-03-17, Eric Gourgoulhon <[email protected] <javascript:>> > wrote: > > On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM, from a fresh git clone > + > > pull develop, parallel (-j8) build OK and make ptestlong resulted in > > ---------------------------------------------------------------------- > > sage -t --long --warn-long 48.9 src/sage/modular/abvar/abvar.py # Timed > out > > sage -t --long --warn-long 48.9 src/sage/modular/abvar/homspace.py # > Timed > > out > > ---------------------------------------------------------------------- > > I got the impression recently that people report time-outs a lot more > frequently than before. But I don't recall if it is all in the same > components (here: modular/abvar). Has there been a regression in specific > parts of Sage? > > Cheers, > Simon > > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
