[Cython] known? 0.16 on varioius platforms: ValueError: Buffer dtype mismatch, expected 'char' but got 'unsigned char' in ...

Yaroslav Halchenko lists at onerussian.com
Tue Jul 17 23:41:34 CEST 2012


Hi everyone!

1. uploaded 0.16 to Debian experimental... many platforms fail with smth
like

,--
| ======================================================================
| FAIL: Doctest: memslice.__test__.test_padded_structs
| ----------------------------------------------------------------------
| Traceback (most recent call last):
|   File "/usr/lib/python2.6/doctest.py", line 2163, in runTest
|     raise self.failureException(self.format_failure(new.getvalue()))
| AssertionError: Failed doctest test for memslice.__test__.test_padded_structs
|   File "/build/buildd-cython_0.16-1-armhf-FpFrv7/cython-0.16/build/work-dir/run/cpp/memslice.so", line unknown line number, in test_padded_structs
|
| ----------------------------------------------------------------------
| File "/build/buildd-cython_0.16-1-armhf-FpFrv7/cython-0.16/build/work-dir/run/cpp/memslice.so", line ?, in memslice.__test__.test_padded_structs
| Failed example:
|     test_padded_structs()
| Exception raised:
|     Traceback (most recent call last):
|       File "/usr/lib/python2.6/doctest.py", line 1253, in __run
|         compileflags, 1) in test.globs
|       File "<doctest memslice.__test__.test_padded_structs[0]>", line 1, in <module>
|         test_padded_structs()
|       File "memslice.pyx", line 42, in memslice.testcase.wrapper (memslice.cpp:3729)
|       File "memslice.pyx", line 1766, in memslice.test_padded_structs (memslice.cpp:27137)
|       File "memslice.pyx", line 1779, in memslice._test_padded (memslice.cpp:27284)
|     ValueError: Buffer dtype mismatch, expected 'char' but got 'unsigned char' in 'ArrayStruct.chars'
`---

more here:
https://buildd.debian.org/status/package.php?p=cython&suite=experimental

I have tested on a sparc box and current master seems to not show this
particular problem (see below though) -- does anyone remember this
particular issue and commit which fixed it?

2. related question -- what is the way with runtests.py to run a particular
unittest? not the full suite (e.g. my specifying memslice in cmdline), but this
particular one, e.g.:

,---
| (sid)yoh at vagus:~/deb/cython/cython$ PYTHONPATH=$PWD/install/lib/python2.7/site-packages/ python runtests.py --no-refnanny -v -v --exclude="parallel" --work-dir=build/work-dir memslice.__test__.test_padded_structs
| Python 2.7.3 (default, Jun 18 2012, 19:31:31)
| [GCC 4.6.3]
|
| Running tests against Cython 0.17pre b0a428d4d438b1ce3e1f5d805b09899377d1ecb5
| Backends: c,cpp
|
|
| ----------------------------------------------------------------------
| Ran 0 tests in 0.001s
|
| OK
| ALL DONE
`---
so I could bisect reasonably fast whenever needed... ?

3. FWIW there are some similar and novel failures on a sparc box on current master:
http://www.onerussian.com/tmp/tests-cython-sparc-0.16rc1-490-gb0a428d.log

I wondered -- do you have any brief instructions on how to setup a local
build bot to contribute back to the cython's Jenkins setup?  Then I could
put a sparc to provide you with CI updates for this platform -- or do you have
a similar one already?


-- 
Yaroslav O. Halchenko
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
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        


More information about the cython-devel mailing list