Robert Bradshaw, 22.11.2010 19:42: > https://sage.math.washington.edu:8091/hudson/job/cython-devel-tests-pyregr-py27-c/ > Any common themes in the failing ones (besides the obvious, e.g. > generators).
It's certainly worth looking through the results. I already noticed a couple of failures that indicate bugs in Cython. One is (once again) due to the tricky str handling rules in Cython and inconsistent usage of EncodedString in the code base. I'm currently looking into that. There also seems to be a problem with the test runner that makes the py3regr tests hang (with --no-fork or XML result output). Apparently, certain test failures leak into subsequent test runs. Running the two tests "test_compileall" and "test_gzip" hangs reliable for me in py3k, after a compiler crash in the first. The weird thing about it is that the gzip test doesn't normally compile because it uses a genexpr in combination with "sorted()", but it compiles without errors after the crash in the compileall test. I faintly remember that we have a way to disable termination on compile errors, maybe that's not getting properly cleaned up here. My current way to work around this is to implement "sorted(genexpr)" as inlined genexpr. ;) Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
