Re: [lxml] [pypy-dev] Looking for clues to consistent Seg Fault in PyPy 2.6.1

Hi, Just an update on this problem. I retested using the latest lxml source from here <https://github.com/lxml/lxml> ( 3.5.0b2?) and a version of PyPy-4.0 from here <https://bitbucket.org/pypy/pypy/downloads/pypy-4.0.0-src.tar.bz2> that I built for Debian 7.9. The good news is I got much farther in the lxml test suite then before, but the bad news is I still encountered my old friend SIGSEGV. This is consistently occuring during test_delslice_negative2 in lxml.tests.test_elementtree.ETreeTestCase which as I said is much further thru the suite of tests then previously. This is encouraging. For now I'm still unable to use this combination so if anyone has a suggestion on how I might proceed to utilize both PyPy and lxml I would be most appreciative. Thanks. - Jeff --------------------------------------------------------- nosetests -vv --nocapture nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] nose.selector: INFO: /home/jeff/lxml/src/lxml/etree.pypy-26.so is executable; skipped nose.selector: INFO: /home/jeff/lxml/src/lxml/objectify.pypy-26.so is executable; skipped Comparing with ElementTree 1.3.0 Comparing with cElementTree 1.3.0 TESTED VERSION: 3.5.0.beta1 Python: (major=2, minor=7, micro=10, releaselevel='final', serial=42) lxml.etree: (3, 5, 0, -99) libxml used: (2, 8, 0) libxml compiled: (2, 8, 0) libxslt used: (1, 1, 26) libxslt compiled: (1, 1, 26) lxml.html.tests.test_autolink.test_suite ... ok lxml.html.tests.test_basic.test_suite ... ok test_allow_tags (lxml.html.tests.test_clean.CleanerTest) ... ok test_clean_invalid_root_tag (lxml.html.tests.test_clean.CleanerTest) ... ok test_safe_attrs_excluded (lxml.html.tests.test_clean.CleanerTest) ... ok test_safe_attrs_included (lxml.html.tests.test_clean.CleanerTest) ... ok lxml.html.tests.test_clean.test_suite ... ok lxml.html.tests.test_diff.test_suite ... ok lxml.html.tests.test_elementsoup.test_suite ... ok ... lots of successful test output removed test_delitem (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delitem_tail (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delslice (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delslice_child_tail (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delslice_memory (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delslice_negative1 (lxml.tests.test_elementtree.ETreeTestCase) ... ok test_delslice_negative2 (lxml.tests.test_elementtree.ETreeTestCase) ... fish: Job 2, “nosetests -vv --nocapture ” terminated by signal SIGSEGV (Address boundary error) --------------------------------------------------------- On Mon, Oct 12, 2015 at 2:30 AM, Armin Rigo <arigo@tunes.org> wrote:
Hi,
On Mon, Oct 12, 2015 at 11:24 AM, Amaury Forgeot d'Arc <amauryfa@gmail.com> wrote:
We define it as a string (in pypy/module/cpyext/include/patchlevel.h) #define PYPY_VERSION "2.6.0-alpha0"
Yes, but i don't know how to do this check in Cython. Well, it's probably easy.
Armin
participants (1)
-
Jeff Doran