I have to guesses: 1. hashing (like Aaron already mentioned) 2. caching
Both are related and responsible for inconsistent results of sympy. Did you try to disable the cache to see if the test passes then? Also, IIRC some tests fail if not executed in correct order (this is bad and why I implemented the --random option for the test runner). Vinzent On 11 Nov., 05:41, smichr <[email protected]> wrote: > When I run the full test suite (e.g. via coverage testing) I get a > failure in a module. When I run tests on that module alone I don't get > the failure. Does anyone have experience with this and know why this > is happening? This is on my github/smichr/1694 branch: > > ________________ sympy\solvers\tests\test_solvers.py:test_multi > ________________ > > File "c:\documents and settings\chris\sympy\sympy\solvers\tests > \test_solvers.p > y", line 433, in test_multi > assert all(eq.subs(zip(syms, a)).n(chop=1) == 0 for a in ans > AssertionError > > tests finished: 2192 passed, 1 failed, 11 skipped, 56 expected to > fail, > 2 expected to fail but passed, in 2099.76 seconds > DO *NOT* COMMIT! > > C:\Documents and Settings\chris\sympy>\s\test solvers.py > > C:\Documents and Settings\chris\sympy>\Python26\python.exe "C: > \documents and set > tings\chris\sympy\bin\test" solvers.py > ============================= test process starts > ============================== > > executable: C:\Python26\python.exe (2.6.4-final-0) > > sympy\solvers\tests > \test_solvers.py[23] ...f................... [OK] > > ======= tests finished: 22 passed, 1 expected to fail, in 17.44 > seconds ======== -- 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.
