Summary: | dev-python/blz-0.6.2 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | [OLD] Unspecified | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick Lauer
2014-12-25 08:13:07 UTC
Well, I bumped this *blz-0.6.2 (02 May 2014) and can only say it must have worked then. pushd to source work/blz-0.6.2-python2_7/lib $ PYTHONPATH=. python2.7 -c "import blz; blz.test()" yields Ran 765 tests in 4.661s \ OK (skipped=3) work/blz-0.6.2-python3_3/lib $ PYTHONPATH=. python3.3 -c "import blz; blz.test()" yields ...........................................................................................................Segmentation fault ditto py3.4. The source "${PYTHON} -c 'import blz; blz.test()'" simply means somewhere in the testsuite. So it appears to be possibly some form of regression in py3. It shouldn't be too hard to at least pin the offending test, seems to be around no. 100 out of 765. I'd prefer to acquire some helpful hints as to what goes on here before filing. They normally say passes fine here. Is this still reproducible? |