This is indeed very odd. Can you run the integrals test with the -v option and let us know which test(s) take so long?
Aaron Meurer On Sun, May 27, 2012 at 5:12 PM, Joachim Durchholz <[email protected]> wrote: > Am 27.05.2012 19:16, schrieb [email protected]: > >> On 27 May 2012 19:09, Joachim Durchholz<[email protected]> wrote: >>> >>> Am 27.05.2012 18:26, schrieb [email protected]: >>> >>>> And I do not get how one run of the tests (integrals) affects >>>> consecutive runs... >>> >>> >>> SymPy has a cache. Later tests reuse results from earlier computations. >>> This has caused problems with reproducing errors in the past, but it does >>> have the advantage that we have a rough estimate of how good SymPy is at >>> returning the same results for the same inputs. >> >> But the cache is not retained between different runs of the test >> runner, is it? Or is it saved to disk? > > > It isn't AFAIK. > It is kept from test to test if you run a suite of tests though. > If it's exerting RAM pressure, that would be an explanation why a test suite > become slow after a few tests. > > Well, that used to be my knowledge. Vlada's response in the other subthread > indicates that it's otherwise. > > Which leaves me clueless about the actual problem in this case. > I guess we'll have to wait until Guru comes back with some numbers. > > > -- > 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. > -- 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.
