[Cython] buffmt.__test__.wrongsize gets stuck after common_include_dir?

[Yaroslav Halchenko]

while trying to re-test Debian package build, in an interactive shell, I
get cython test stuck at:

...
Doctest: buffmt.__test__.wrongsize ... ok
runTest (__main__.EndToEndTest)
End-to-end basic_cythonize ... ok
runTest (__main__.EndToEndTest)
End-to-end basic_distutils ... ok
runTest (__main__.EndToEndTest)
End-to-end build_dir ... ok
runTest (__main__.EndToEndTest)
End-to-end common_include_dir ...

tests were executed using

runtests.py --no-refnanny -v -v --exclude="parallel" --work-dir=build/work-dir

any clues?  is it multiprocessing to blame again?

/bin/bash /tmp/hooks/C10shell
  /bin/bash
    /usr/bin/make -f debian/rules binary
      /usr/bin/perl -w /usr/bin/dh binary --with python2,python3 --buildsystem python_distutils
        /usr/bin/make -f debian/rules override_dh_auto_test
          /bin/sh -c set -e; for P in 2.7 3.4; do \          echo "PYTHON: $P"; \  export; \  PYTHONPATH=`/bin/ls -d /tmp/buildd/cython-0.20.2/build/lib.*-$P` \   /usr/bin/python$P runtests.py --no-refnanny -v -v --exclude="parallel" --work-dir=build/work-dir; \ done
            /usr/bin/python2.7 runtests.py --no-refnanny -v -v --exclude=parallel --work-dir=build/work-dir
              /bin/sh -c /usr/bin/python2.7 setup.py build_ext --inplace
                /usr/bin/python2.7 setup.py build_ext --inplace
                  /usr/bin/python2.7 setup.py build_ext --inplace
                  /usr/bin/python2.7 setup.py build_ext --inplace


-- 
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,            Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik