When it does reproduce, is it always this particular test?
On Wed, Nov 30, 2016 at 6:46 AM, Yaroslav Halchenko
wrote:
> A fresh one I ran into while rebuilding with fixes for 32bit (thanks
> BTW! sorry for not prompt followup/gratitude)
>
> ==
> ERROR: runTest (__main__.CythonRunTestCase)
> compiling (cpp) and running builtin_subtype_methods_T653
> --
> Traceback (most recent call last):
> File "runtests.py", line 998, in run
> self.run_tests(result, ext_so_path)
> File "runtests.py", line 1013, in run_tests
> self.run_doctests(self.module, result, ext_so_path)
> File "runtests.py", line 1023, in run_doctests
> run_forked_test(result, run_test, self.shortDescription(), self.fork)
> File "runtests.py", line 1076, in run_forked_test
> cid, result_code = os.waitpid(child_id, 0)
> OSError: [Errno 4] Interrupted system call
>
> --
> Ran 581 tests in 188.225s
>
> FAILED (errors=1)
>
> it is not 100% reproducible. Rebuilding the package went smooth without this
> hiccup. Just wanted to let you know
>
> might be related that the tests were ran as
>
>
> set -e; for P in 2.7 3.5; do \
> PYTHONPATH=`/bin/ls -d /build/cython-0.25.2~b0/build/lib.*-$P` \
> /usr/bin/python$P runtests.py --shard_count=16 \
> --no-refnanny -v -v --exclude="(parallel|Debugger|annotate_html)"
> --work-dir=build/work-dir 2>&1; \
> done
>
> so testing in parallel to speed up the build of the package. This one was
> the
> only failure I have ran into but it built fine before (but there could have
> been some changes in the core packages since then)
>
> --
> Yaroslav O. Halchenko
> Center for Open Neuroscience http://centerforopenneuroscience.org
> 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
> ___
> cython-devel mailing list
> cython-devel@python.org
> https://mail.python.org/mailman/listinfo/cython-devel
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel
