[sympy] slow tests before commit

2013-02-20 Thread Mary Clark
I'm nearly ready to submit my patch, and I've been trying to run the slow tests. However, they are taking hours (literally). I ran them overnight, and after eight hours they had still not finished. Is this normal, or is there something wrong with my computer/my code? Mary -- You received

Re: [sympy] slow tests before commit

2013-02-20 Thread Mary Clark
Yeah, I just ran Travis, and everything passed. :) -- You received this message because you are subscribed to the Google Groups sympy group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email

Re: [sympy] slow tests before commit

2013-02-20 Thread Aaron Meurer
The slow tests are exactly that: slow. They are disabled by default for a reason. We only run them before a release, or if we suspect a change might affect them. And even if you do run them, I recommend using the timeout flag. Because at least one test takes a *really* long time. Aaron Meurer

Re: [sympy] slow tests before commit

2013-02-20 Thread Prasoon Shukla
On Wednesday, February 20, 2013 9:06:37 PM UTC+5:30, Aaron Meurer wrote: The slow tests are exactly that: slow. They are disabled by default for a reason. We only run them before a release, or if we suspect a change might affect them. Does that mean some tests are disabled by default?

Re: [sympy] slow tests before commit

2013-02-20 Thread Aaron Meurer
Yes. Tests that show up as a w are skipped because they are slow. Tests that show up as a k are skipped for some other reason (usually because some dependency like Numpy is not installed). You can run bin/test with the -v option for more information. You generally don't need to worry about these,