It seems to me that a possible way to reduce the average time of tests could be to test only the modules which depend on the modified modules. I do not know how long it would take to build the dependency tree; if it takes too much, it could be stored. Making tests when only a leaf of the tree is modified would be fast.
On Friday, February 22, 2013 10:09:54 PM UTC+1, Ondřej Čertík wrote: > > Dear Travis-CI support team, > > For the sympy repository: > > https://travis-ci.org/sympy/sympy/builds > https://travis-ci.org/sympy/sympy/pull_requests > > it looks like that tests are running, but people seem to keep updating > PRs more often than Travis can run the tests, > and so there is now more and more scheduled runs in the queue. > > The reason is probably that our tests take quite a while to run. What > is the Travis policy on this? > We sent some donation to you a few months ago and we would be happy to > send more, if that would help. > The other option is for us to refactor our test suite so that it works > better with Travis-CI. > What would be reasonable time limits that you think we should get under? > > Thanks for any help, > Ondrej Certik > http://sympy.org/ > -- 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.
