Hi, On Sat, Nov 8, 2014 at 11:59 AM, Stefan Behnel <stefan...@behnel.de> wrote: > Yury V. Zaytsev schrieb am 08.11.2014 um 18:55: >> On Sat, 2014-11-08 at 00:53 +0100, Stefan Behnel wrote: >>> >>> Also, compiling the resulting C code with CFLAGS="-O0" (or "-O0 -ggdb" >>> etc.) usually gives another speed boost for testing purposes. >> >> Just to mention it, the compilation is certainly going to be much >> faster, but the resulting code might end up being a lot slower, so if >> you then run a battery of tests that uses the module, you might end up >> loosing way more than you gained by cutting down the compilation time. > > My assumption was that the test suite doesn't include performance tests and > that it is small and concise enough to exercise most code paths only a > couple of times, with only some core code paths being heavily used. That > tends to be reasonable (I've yet to see a code base with a branch coverage > of 100%), but will obviously not apply to all packages. If you have test > for large data sets, for example, the performance may suffer noticeably, as > you say. > > It's usually worth comparing, though.
I have the same build error on a real machine: http://nipy.bic.berkeley.edu/builders/dipy-py3.4/builds/49/steps/shell_5/logs/stdio Is there anything you can suggest to help debug? Cheers, Matthew _______________________________________________ cython-devel mailing list cython-devel@python.org https://mail.python.org/mailman/listinfo/cython-devel
