[issue1421] pypy latest trips over pyftpdlib-1.0.1 storage related tests
New submission from Ian Delaney <della5@iinet.com.au>: in the test suite comprising of all of 2 test files, it trips over here test_appe_rest (__main__.TestFtpStoreDataMProcMixin) ... ok test_failing_rest_on_stor (__main__.TestFtpStoreDataMProcMixin) ... ok test_quit_during_transfer (__main__.TestFtpStoreDataMProcMixin) ... ok test_rest_on_stor (__main__.TestFtpStoreDataMProcMixin) ... ^X^C It persistently hangs on (a number of) tests testing stor(age) of data and I have no idea where to start. fijal, you made a package called ctypes_configure who know when. It's been made a dep to tests for pyzmq but I can't add it to portage since it lacks both a live homepage and a license. Plse shoer it up. ---------- assignedto: fijal messages: 5447 nosy: fijal, idella5, pypy-issue priority: performance bug release: 2.0 status: chatting title: pypy latest trips over pyftpdlib-1.0.1 storage related tests ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
Fijal <fijall@gmail.com> added the comment: pyzmq these days depends on cffi (for pypy at least), ctypes_configure should not be used any more. Cheers, fijal ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
Ian Delaney <della5@iinet.com.au> added the comment: ak ok, I suppose I have to tease out any tests that dep on ctypes_configure. what of this hanging with the testsuite? Is it something you can fix or those at pyftpdlib should re=write to cater to pypy? ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
On Fri, Mar 15, 2013 at 1:03 AM, Ian Delaney <tracker@bugs.pypy.org> wrote:
Ian Delaney <della5@iinet.com.au> added the comment:
ak ok, I suppose I have to tease out any tests that dep on ctypes_configure.
what of this hanging with the testsuite? Is it something you can fix or those at pyftpdlib should re=write to cater to pypy?
cffi is better these days, I can probably put ctypes_configure website somewhere though. It's pycon now though so later :)
Ian Delaney <della5@iinet.com.au> added the comment: I don't quite follow. ctypes_configure should not be used any more, however you consider re-introducing ctypes_configure to a website, the only package with 'pycon' is pyconstruct which I'd have thought is totally distinct. and pyftpdlib tests re pypy? ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
Fijal <fijall@gmail.com> added the comment: ctypes_configure should not be used, but it does not mean it should not have a website (it won't be endorsed on the pypy website though) as for pycon - it's a conference we're all attending so response times are slow :) ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
Ian Delaney <della5@iinet.com.au> added the comment: ah, a conference, I see. I filed at pyzmq and a maintainer there has sorted it out and removed ctypes_configure seemingly from my prompt since your ctypes_configure was hardcode imported in a core module. ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
mattip <matti.picus@gmail.com> added the comment: issue cleanup - marking this as resolved. Please reopen if needed. ---------- nosy: +mattip status: chatting -> resolved ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
Armin Rigo <armin.rigo@gmail.com> added the comment: mattip: I would not blindly close issues; I'd rather that we try to reproduce the original reported issue, and only close issues where that is not reasonably possible (or, of course, where we can see that the bug disappeared in the meantime). If you tried but can't for some reason, please explain it in the closing message. ---------- nosy: +arigo status: resolved -> chatting ________________________________________ PyPy bug tracker <tracker@bugs.pypy.org> <https://bugs.pypy.org/issue1421> ________________________________________
participants (5)
-
Armin Rigo -
Fijal
-
Ian Delaney
-
Maciej Fijalkowski -
mattip