Absolutely. I was thinking that there was a decently sized set of tests that were going to be run regularly without the cache in which case it might make sense to introduce another mark/option but if it's only a few than specifying them manually is probably better.
On Wed, May 6, 2015 at 12:45 PM, Aaron Meurer <[email protected]> wrote: > Can't you do ./bin/test -C <set of tests>? > > Aaron Meurer > > On Wed, May 6, 2015 at 11:46 AM, Peter Brady <[email protected]> > wrote: > > Not really, caching is a decision made at import time (there's probably a > > more precise language for this). I think there are two options here: > > > > 1) Write a context manager that forces calls to f.__wrapped__ rather > than f > > so that the cache is bypassed. This may not be possible. > > > > 2) Have a set of tests run without the cache and add the option to > bin/test > > to select them. This is definitely possible. > > > > > > On Wednesday, May 6, 2015 at 12:56:58 AM UTC-6, Joachim Durchholz wrote: > >> > >> I'm currently tutoring PR #9376, which fixes a bug that happens only > >> when caching is turned off. > >> We're trying to figure out a way to write a regression test. Our test > >> suite is run with caching switched on, even on Travis, so we need a way > >> to make sure that this single test is running with caching switched off. > >> > >> I gather that the test framework does clear_cache() before each test, > >> but that's not enough - the test seems to be filling the cache on its > >> own, and enough to break the infinite recursion that will happen without > >> caching. So we really need to disable the caching machinery on a > >> per-test basis. > >> Does such a feature exist? > > > > -- > > 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. > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/sympy/cf05bc44-b413-4f27-8e25-3194fa4d71e6%40googlegroups.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sympy" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sympy/xPAhw28bPDc/unsubscribe. > To unsubscribe from this group and all its topics, 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/CAKgW%3D6J8gb1ihH4neFhqZjV%2Bx%3DUX%2B%3Dy7W81pExF9a8dJLUyMSw%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CALoNiQfidr4ryG1%3DRLe9dmeCCbsvLU8q33aHvbArc1vkf1XwhQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
