Hi, I never heard back from the Travis support guys, but it looks like Travis has caught up, so all is good now. Implementing any of the things below would however help anyway.
Ondrej On Sat, Feb 23, 2013 at 6:21 PM, Ondřej Čertík <[email protected]> wrote: > Hi, > > Thanks everybody for a feedback. I think a few things we should > definitely do now: > > * measure time of each test and report it in some form (e.g. print > tests in ascending order by their execution time at the end...) > > * Skip a few of the longest running tests on Travis --- I think it > should be possible to speedup the overall execution considerably > (maybe from 40min to 15min?) > > * See if we need the long running tests at all --- maybe it is > possible to refactor the test to still test the same functionality but > be fast? > If not, then those would be very good candidates in SymPy for big > speedup. I would be very interested in identifying such parts of > SymPy. > > Ondrej -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
