I've recently added code to print enhanced tracebacks when we kill a test due to timeout (#23208), if you have gdb installed then you'll get some idea of what it was doing when it timed out. I've seen a few cases on the buildbot that point to FFPACK::CharPoly. This might be a bug in linbox that rarely occurs, or maybe we are picking data like unlucky primes for some reason (though that alone shouldn't cause the timeout).
In any case: install gdb on your patchbots to get more information about timeouts https://trac.sagemath.org/ticket/23391 On Saturday, July 8, 2017 at 7:34:16 PM UTC+2, Kwankyu Lee wrote: > > I observed another "Timed out" on a patchbot: > > sage -t --long src/sage/graphs/matchpoly.pyx > Timed out > > On my laptop, this takes just less than 5 seconds. Strange... > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
