As an (mostly unrelated) notice, the tests will get faster once gsoc-3
is merged.
On 26.12.2011 14:03, Aaron Meurer wrote:
On Mon, Dec 26, 2011 at 3:41 AM, Joachim Durchholz<[email protected]> wrote:
Am 26.12.2011 01:25, schrieb Aaron Meurer:
There was a @slow decorator recently added, yes.
Ah, I see. I wasn't aware of the distinction between slow and fast tests.
(Running test --slow right now :-) )
However, the tests just got slower because I just pushed in Tom's
gsoc-2 branch. If any single test is running too slow, we can add
@slow to it.
Okay.
What's the policy for marking a test slow or not?
@slow seems to have been assigned inconsistently: some slow tests are not
marked, some marked tests aren't slow.
@slow is brand new (a result of one of the GCI tasks), so it hasn't
been applied consistently yet. In particular, it was added after Tom
did his work, so some new tests may need it that don't have it. If
there is a test that you think should be marked or unmarked with
@slow, feel free to open a pull request.
Aaron Meurer
Regards,
Jo
--
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.
