You could skip it, or honestly you could also mark it as slow. The GCI student who implemented slow tests made it so that a keyboard interrupt kills only the one test, and he also implemented a timeout option, so it should be able to handle such a test just fine. There have been others who have disagreed with though, so don't take my word as final on it.
Aaron Meurer On Jun 16, 2012, at 7:24 AM, "[email protected]" <[email protected]> wrote: > I suppose that the slow flag is for tests that actually pass, however > slowly. What to do for a test that simply hangs? > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
