Hi, On Fri, Aug 16, 2013 at 6:29 AM, Jason Moore <[email protected]> wrote: > We could setup Travis to test each slow test in a separate build giving up > to 50 mins for installation + testing a single test. If the tests are slower > than 50 mins, then we can forget them. In the case of mechanics it would be > very useful for us to have slow tests, as we can then check a benchmark > problems that puts all of our code through the ringer. I find tests like > these to be much more robust than smaller unit tests for our case. Testing > the all of the smaller pieces of the code individually does a lot of good > but there are just too many possible combinations of options to thoroughly > unit test. A "big" test with a known answer is really helpful for us. > > Another option would be to drop Travis and use something like Jenkins that > we install on our own server(s). Then we will not have time limits and have > more freedom to do anything with the build setup.
Or run nightly slow tests on trunk using something like Jenkins or buildbot. Would the Sage team let you run some jobs on their machines? I'm happy to host sympy builds on our buildbot setup. Cheers, Matthew -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
