On Wed, Aug 12, 2015 at 08:29:28PM +0200, Didier 'OdyX' Raboud wrote:
> Le mercredi, 12 août 2015, 16.00:22 Goswin von Brederlow a écrit :
> > > Le jeudi, 6 août 2015, 14.40:10 Goswin von Brederlow a écrit :
> > > > every now and then pyside crashes with a segfault. Most often
> > > > because
> > > > it doesn't play nice with the python GC and widgets have to keep
> > > > python objects stored in C++ alive manually. But sometimes it
> > > > isn't obvious where and why pyside segfaults. For those it would
> > > > be nice if one could use python3-dbg and get better gdb backtraces
> > > > for the application. But this requires a debug build of pyside.
> > > >
> > > > Please provide a debug build of pyside.
> > >
> > > Since 1.0.9-2, debug packages are not built anymore, as they were
> > > huge to build and resulted in insanely big binary packages, see
> > > http://snapshot.debian.org/package/pyside/1.0.9-1/ .
> >
> > The -dbg build got " 1% tests passed, 405 tests failed out of 408".
> > Lots of failures in refrence counts, tests/QtGui/qmainwindow_test.py
> > and tests/QtWebKit/shouldInterruptjavascript_test.py hang and need to
> > be manually killed, lots of segfaults in the tests and finally:
>
> Yes. This was the other problem with debug builds: there is something
> fishy going on with python-dbg builds and tests. Upstream is basically
> unresponsive and I'm reaching my limits (in terms of competences, as
> well as motivation).
>
> Frankly, I'm only a PySide maintainer because I was initially interested
> in it in the context of debian-mobile, but I'm not at all using PySide
> (although I like the idea of doing Qt in python). So the status is "not
> actively involved, but welcoming patches". I'm happy to hand
> maintainership over too, only staying because I feel responsible
> (although less and less).
>
> > When was the last time you did a debug build?
>
> For 1.0.9-2, apparently.
>
> > PS: That's why I want debug packages from the start no matter how big
> > they are. If they aren't autobuild then by the time you need them they
> > don't work.
>
> I welcome patches though??? :) I know it's an easy answer, but that's the
> best one I can offer.
>
> Cheers,
> OdyX
If I get a spare hour somewhere I can send patches for the control
file and .install file fixes easy enough. The test suite failures get
ignored so that isn't a stopper. I tested the resulting debs with
python3-dbg and they work fine. So it's something fishy in the test
suite itself as you suggest. I would suggest not running them for
-dbg package because like you I don't care enough to fix something
that complicated and fishy. I would suggest not running them for
-dbg package because like you I don't care enough to fix something
that complicated and fishy.
The blocking tests are the main problem. I don't know why but I see
that in basically every single test suite out there. None of them seem
to come with a default timeout out of the box so any hanging test will
hang forever. And usualy the test suite frameworks are hugely complex
that adding that feature is not trivial. I'm not sure if I will find
the time and motivation to delve that deep into it any time soon.
I didn't check the build log closely but since PySide autobuilds
without debug it seems likely that the test cases only hang for debug
packages. So disabling the test suite for them might be a quick fix
for that problem too. That's probably easy enough to try.
MfG
Goswin
