Very slow cq_test, slicq_test

[smallnamespace]

For example, on Windows10 / AMD64, running python -m unittest discover -s tests -p cq_test.py results in tests taking something like ~10-20 minutes to finish. Is this normal?

[grrrr]

Hi, these are exhaustive tests that are only done once. As far as i remember, they don’t take as long on my linux machine, but you can also leave them out if you wish.

Am 17.11.2015 um 03:10 schrieb smallnamespace notifications@github.com:

For example, on Windows10 / AMD64, running python -m unittest discover -s tests -p cq_test.py results in tests taking something like ~10-20 minutes to finish. Is this normal?

—
Reply to this email directly or view it on GitHub #10.

[smallnamespace]

Well, I think potential contributors would want the ability to run all the tests and know they're not breaking things :)

Right now the test runs just the first 2 test cases and then completely hangs for me (for like >1 hour). Fine if I make modifications to the test to get it running in a reasonable amount of time?

[grrrr]

Hi, the test should definitely not hang.
Of course you are welcome to contribute a pull request to whatever aspect of the project.

[smallnamespace]

Thanks! Just want to check with you first in case you had objections.

To give me a rough guideline, how long does cq_test take to run for you? I don't have a working copy of PyFFTW3, so I'm trying to figure out whether the slowdown is from the FFT or somewhere else.