On 19 June 2012 00:24, Aaron Meurer <[email protected]> wrote: > 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.
There are two constraints for me: - I can dedicate one of the two cores to testing 24/7 (it is stated to be a 2GHz core), however it should be sequential and it should not take more than about 200-300 MB RAM. This means that something that is awfully slow will slow down also the current PR tests. - The automation script (tox, bot, whatever) should be already written (or really trivial to write). So if you have any ideas (slow tests, documentation builder, installing tox, etc) just mention them and I will add them. -- 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.
