Re: qtdeclerative tests fails on various archs
Hi all, On Thu, Oct 06, 2016 at 11:32:23AM +0200, Allan Sandfeld Jensen wrote: > In the first one 32-bit big-endian doesn't work. I assume that is before my > patch, and in the second all the 64-bit non x64 platforms fail, including the > little endian? Yes, in the first one (5.6.1) there are failures on 32-bit big-endian archs. We do have your change cherry-picked (as fix-V4-on-big-endian.patch), but we do not have https://codereview.qt-project.org/162712, so the broken setTag() / setValue() methods are still there. I will try fixing them when I have time. The second one (5.7.0) should get a lot better soon: some failures were because of symbols diffs, I have just done a new upload to fix them (this upload also backports a patch to fix arm64). -- Dmitry Shachnev signature.asc Description: PGP signature -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: qtdeclerative tests fails on various archs
On Thursday 06 October 2016, Sandro Knauß wrote: > > @Allan: You can find the buildlogs for different archs on debian: > https://buildd.debian.org/status/package.php?p=qtdeclarative-opensource-src > and > https://buildd.debian.org/status/package.php?p=qtdeclarative-opensource-src > &suite=experimental > In the first one 32-bit big-endian doesn't work. I assume that is before my patch, and in the second all the 64-bit non x64 platforms fail, including the little endian? Do I read that right? -- The Qt Company Rudower Chausse 13, 12489 D-Berlin -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: qtdeclerative tests fails on various archs
Hey, > Actually, it looks like Sandro’s adding fix-V4-on-big-endian.patch made > things worse on powerpc. > > After removing that patch, it is possible to create a QQmlEngine. > > Many tests are however still failing: > https://people.debian.org/~mitya57/qtdeclarative-powerpc-tests-log.txt I added this patch because upstream (Allan Jensen) said, this patch would/ could help: "For the second issue with big-endian. The test that fails tries to use QJSEngine which doesn work, and as far as I can tell you are not running the tests on qtdeclarative either. I tried looking into it, and I think this solves it: https://codereview.qt-project.org/#/c/170754 Atleast it works on qemu powerpc. " @Allan: You can find the buildlogs for different archs on debian: https://buildd.debian.org/status/package.php?p=qtdeclarative-opensource-src and https://buildd.debian.org/status/package.php?p=qtdeclarative-opensource-src&suite=experimental Regards, sandro signature.asc Description: This is a digitally signed message part. -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk
Re: qtdeclerative tests fails on various archs
Hi Sandro, On Fri, Sep 30, 2016 at 09:38:21AM +0200, Sandro Knauß wrote: > Hey, > > now after we manged it to get the auto tests running for qtdeclarative > (5.6.1-10) on some archs. Other archs are still failing to run the tests with: > > [...] > make[6]: Entering directory '/«PKGBUILDDIR»/tests/auto/qml/parserstress' > /«PKGBUILDDIR»/tests/auto/qml/parserstress/target_wrapper.sh > ./tst_parserstress > Makefile:362: recipe for target 'check' failed > make[6]: *** [check] Segmentation fault > make[6]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qml/parserstress' > > (happens on: mips, powerpc, alpha, freebsd, sparc64, x32 - have they anything > in common? ) > > I'm a little bit glueless why the start of the tests would fail on some archs. Yesterday I filed two bugs for this: https://bugreports.qt.io/browse/QTBUG-56264 (sparc64, see also comments there) https://bugreports.qt.io/browse/QTBUG-56271 (powerpc) I will try to do more debugging on porterboxes when/if I have time. -- Dmitry Shachnev signature.asc Description: PGP signature -- http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk