Am 24.07.2013 20:44, schrieb Joachim Durchholz:
Oh, I can run the tests no problem.
The issue is that whenever I do a cross-cutting change, I need to run
the full test suite, and I won't know whether I broke anything until a
full day later. That's going to slow down progress quite a bit.
But if 40,000 seconds for a full test suite are normal, I guess it can't
be helped. *sigh*
In fact, I now find that after 48 hours of continuous grind, the test
simply crashes with no result:
~/workspace/sympy$ bin/test --slow
=====================================================================
test process starts
=====================================================================
executable: /usr/bin/python (2.7.3-final-0) [CPython]
architecture: 64-bit
cache: yes
ground types: python
random seed: 95852297
hash randomization: on (PYTHONHASHSEED=2349520526)
sympy/assumptions/tests/test_query.py[1] . [OK]
sympy/core/tests/test_wester.py[6] ...... [OK]
sympy/functions/elementary/tests/test_trigonometric.py[2] .. [OK]
sympy/integrals/tests/test_failing_integrals.py[8] fXf~/workspace/sympy$
The running image had a memory footprint of 1.9 GB last time I looked at
it. Is this normal, or should I look how my lastest changes may have
introduced that?
(I'm currently running bin/test --slow test_failing_integrals but that
will take another two days until I know for sure.)
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
