SegFault when running Scrapy tests.

Hi all, I'm starting a new thread because the last one seems to be on a new topic. I was just trying out the scrapy unit tests in PyPy and I've run into some segfaults. To reproduce, download and install Scrapy: https://github.com/scrapy/scrapy Then run this in the tests directory: /usr/local/pypy/bin/trial test_http_request.py I haven't found the exact source of the issue yet, but I'm posting this in case somebody can find it faster. Thanks, -Joe

On Fri, Dec 14, 2012 at 8:24 PM, Joe Hillenbrand <joehillen@gmail.com> wrote:
Hi all,
I'm starting a new thread because the last one seems to be on a new topic.
I was just trying out the scrapy unit tests in PyPy and I've run into some segfaults.
To reproduce, download and install Scrapy:
https://github.com/scrapy/scrapy
Then run this in the tests directory:
/usr/local/pypy/bin/trial test_http_request.py
I haven't found the exact source of the issue yet, but I'm posting this in case somebody can find it faster.
Thanks,
-Joe _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Hi Thanks for the report. I'm running some tests to see what's going on, however, can you please submit it to bugs.pypy.org so it doesn't get lost? For what is worth, it might be related to cpyext and lxml.

On Fri, Dec 14, 2012 at 9:38 PM, Maciej Fijalkowski <fijall@gmail.com> wrote:
On Fri, Dec 14, 2012 at 8:24 PM, Joe Hillenbrand <joehillen@gmail.com> wrote:
Hi all,
I'm starting a new thread because the last one seems to be on a new topic.
I was just trying out the scrapy unit tests in PyPy and I've run into some segfaults.
To reproduce, download and install Scrapy:
https://github.com/scrapy/scrapy
Then run this in the tests directory:
/usr/local/pypy/bin/trial test_http_request.py
I haven't found the exact source of the issue yet, but I'm posting this in case somebody can find it faster.
Thanks,
-Joe _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
Hi
Thanks for the report. I'm running some tests to see what's going on, however, can you please submit it to bugs.pypy.org so it doesn't get lost?
For what is worth, it might be related to cpyext and lxml.
Hi Joe It crashes somewhere in the error recovering code of lxml. Chances are either cython or lxml do something that pypy is unhappy about. We're just discussing a medium-term plan how to fight with such issues (it migth be a missing incref in a place where CPython doesn't care for example), however for now fixing cython and/or lxml seems like the only option. Cheers, fijal

Hi Joe
It crashes somewhere in the error recovering code of lxml. Chances are either cython or lxml do something that pypy is unhappy about.
We're just discussing a medium-term plan how to fight with such issues (it migth be a missing incref in a place where CPython doesn't care for example), however for now fixing cython and/or lxml seems like the only option.
Cheers, fijal
Thanks for the quick response on this. I'll definitely write a bug.

On Fri, Dec 14, 2012 at 11:39 PM, Joe Hillenbrand <joehillen@gmail.com> wrote:
Hi Joe
It crashes somewhere in the error recovering code of lxml. Chances are either cython or lxml do something that pypy is unhappy about.
We're just discussing a medium-term plan how to fight with such issues (it migth be a missing incref in a place where CPython doesn't care for example), however for now fixing cython and/or lxml seems like the only option.
Cheers, fijal
Thanks for the quick response on this. I'll definitely write a bug.
That said, it might as well be a cpyext bug, you can't tell until you identify it. It's just that cpyext has generally less priority than other stuff (although see the other thread, maybe we can do something about it).
participants (2)
-
Joe Hillenbrand
-
Maciej Fijalkowski