On May 26, 2012, at 12:19 PM, Ronan Lamy <[email protected]> wrote:
> Le samedi 26 mai 2012 à 13:03 -0500, Guru Devanla a écrit :
>
>> I did not pass any arguments while running the test.
>>
>> Here is what gets printed in the header:
>
>> executable: /usr/bin/python (2.7.1-final-0)
>> architecture: 32-bit
>> cache: yes
>> ground types: python
>> random seed: 17908803
>
>> Also, I printed out the list of all the options that were set :
>
>> {'sort': True, 'slow': False, 'verbose': False, 'cache': True,
>> 'colors': True, 'seed': None, 'kw': '', 'timeout': False,
>> 'force_colors': False, 'tb': 'short', 'pdb': False, 'types': None}
>
> That seems normal.
>>
>> I will try to time the other tests and share that info when I run them
>> again.
>
> We have a few tests that are meant to take very long instead of failing.
> Maybe you're triggering one of these pseudo-failures. Does it take as
> long when you test "master"? How long does it take to run 'bin/test
> sympy/core' (shouldn't be more than a minute)?
That's a good point. You may be running the slow test for some
reason. When you run the tests, you should occasionally see a blue w
(instead of a . or an f). There is one in
sympy/assumptions/tests/test_query.py for example. Under normal
testing conditions, these should be skipped. So check if these are
the tests that are taking so long. You can run them manually with
./bin/test --slow.
Aaron Meurer
--
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.
