I think the slow tests have to be run separately. I would recommend running with some timeout, as some of the tests might hang. It depends on your configuration, and how long the tests take. Five or ten minutes should be fine, I think.
Also, if you've got a ton of spare cycles, we could try testing other things as well, such as building the docs. Aaron Meurer On Jun 18, 2012, at 3:25 PM, "[email protected]" <[email protected]> wrote: > The api issues are almost dealt with (huge thanks to Michael Mayorov) > and I will soon start again running the automated script. My question > is whether I should also start running the slow tests? The machine I > am using runs the normal tests in about 20-25 minutes (more for > python3 until a certain pull request gets merged). I was thinking > about doing the following: > > - test 2.7 with numpy, matplotlib and gmpy (20 minutes) > - test 2.5 with slow tests (20 minutes + slow tests) > - test 3.2 (35 minutes) > > What configuration (flags, timeout, etc) do you suggest for the slow tests? > > -- > 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.
