Closed ZeroChaos- closed 4 years ago
Hi. I was hoping to grab shiboken2 and pyside2 and put them in Gentoo,
Oh, blessed news!
...but the test failures appear significant.
...oh, bugger. I must confess that I've never actually run these tests myself. The massive failures you've exhibited above are both edifying and terrifying – but probably also ignorable. I and the fine gentle(wo)men at the ::waebbl
overlay can assure everyone here that the shiboken2
, pyside2
, and pyside2-tools
ebuilds all behave as expected – and have for the past several years. In particular, ebuilds for:
::waebbl
work basically well, open issues notwithstanding.Clearly, there's a critical disconnect between unit tests in the shiboken2
test suite and the actual real-world robustness of shiboken2
. If I had to venture an uneducated guess, it would be that The Qt Company has expanded the shiboken2
test suite to cover future edge cases and feature requests not currently required by PySide2.
Nokia's original vision for shiboken
was always as a general-purpose C++ -> Python binding generator deployed by a diverse ecosystem of downstream Python projects – not just PySide. That idyllic utopian vision never happened, of course. PySide2 is still the only downstream Python project to directly leverage shiboken2
....to my limited knowledge.
The Qt Company would probably very much like it if multiple projects began requiring shiboken2
, as the maintenance burden would then be somewhat shifted off their industrious shoulders and onto the volunteer open-source community as a whole. Ergo, hypothetical shiboken2
unit tests exercising features that PySide2 doesn't currently need but other downstream clients might.
Or maybe the shiboken2
test suite is just totally b0rked. It's hard to see that happening, because this is The Qt Company. All in all, I can only give a noncommittal shrug as depicted here in XML: </noncommittal_shrug>
You might try redirecting this issue to the upstream Qt bug tracker. Ask for Christian Tismer if you do. He's a jolly good Pythonista and always delighted to help the Linux community out.
Thanks for the detailed report all the same, @ZeroChaos-! Always fun to see a fellow DEFCONner lurk out of the shadows. :eyeglasses:
See commentary at #87 with apologies. Cue sad cat face. :crying_cat_face:
of note, RESTRICT=test is probably a saner solution than https://github.com/leycec/raiagent/commit/bd40c0ace9b5d9bd07430007a554c3f053365671 while you know the tests are broken. I always hate to remove things knowing they will have to be added back anyway.
Ah-ha! I knew there had to be a simpler way; I'd completely forgotten about that ebuild variable. If only I had known what I now know. I'll promptly revert bd40c0a and add RESTRICT=test
to the preamble for these ebuilds, as you suggest.
Teamwork: it's awesome.
Done and done.
Hi. I was hoping to grab shiboken2 and pyside2 and put them in Gentoo, but the test failures appear significant. Can you please share your thoughts?