I think the best option is to fix the sigalarm delivery to be 100% reliable
On Thursday, May 29, 2014 2:34:13 PM UTC+1, Ralf Stephan wrote: > > On Thu, May 29, 2014 at 12:28 PM, Volker Braun > <vbrau...@gmail.com<javascript:> > > wrote: > >> The reason is alarm() not working reliably. The failing test is from: >> >> 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over >> GF(2**k) and cannot be interrupted >> >> but thats just the symptom not the cause. >> > > So, should one be able to switch off those tests by giving a test > option? Or do you think it's solvable somehow to make it work in a VM? If > neither, patchbot should get some ignoring logic. What do you think best? > > -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
