| Summary: | dev-qt/qtbase-6.5.2-r2: fails 2 tests on arm (tst_qpainter, tst_qlineedit) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sam James <sam> |
| Component: | Current packages | Assignee: | Qt Bug Alias <qt> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | ionen |
| Priority: | Normal | Keywords: | TESTFAILURE |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 914026 | ||
| Attachments: |
build.log.xz
LastTest.log.xz |
||
|
Description
Sam James
2023-09-11 22:53:02 UTC
Created attachment 870327 [details]
LastTest.log.xz
FAIL! : tst_QPainter::fpe_radialGradients() '!exceptions' returned FALSE. (Floating point exception: Invalid operation) Loc: [/var/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/gui/painting/qpainter/tst_qpainter.cpp(2872)] I couldn't immediately spot what the qlineedit error is. (In reply to Sam James from comment #2) > FAIL! : tst_QPainter::fpe_radialGradients() '!exceptions' returned FALSE. > (Floating point exception: Invalid operation) > Loc: > [/var/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/ > tests/auto/gui/painting/qpainter/tst_qpainter.cpp(2872)] > > I couldn't immediately spot what the qlineedit error is. Had me confused for a sec too but XPASS : tst_QLineEdit::testQuickSelectionWithMouse() QCOMPARE(lineEdit.selectedText(), partialSelection) returned TRUE unexpectedly. Loc: [/var/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/widgets/widgets/qlineedit/tst_qlineedit.cpp(5044)] While in my own tests I get: PASS : tst_QLineEdit::testQuickSelectionWithMouse() fwiw Void Linux been skipping tst_qlineedit, albeit I don't know why. Not that a mouse selection test sound concerning. For qpainter, it's just testing for catching exception if I get this right (e.g. divide by zero) probably tried something that doesn't work here. I think neither are worth worrying or pursuing, and I'm thinking to skip these. My guess is the SIGFPE varies based on vectorisation/neon/whatever, was worried at first it might be some confusion based on maybe armv8 host but I feel like we'd see other breakage if so, and such things will probably only show up on other devices anyway. Fine with me to skip them, it's not a bad baseline at all anyway given arm32 gets tested a bit less nowadays. Cheers! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=19522155671362720c52756abb409373c135b325 commit 19522155671362720c52756abb409373c135b325 Author: Ionen Wolkens <ionen@gentoo.org> AuthorDate: 2023-09-12 00:07:29 +0000 Commit: Ionen Wolkens <ionen@gentoo.org> CommitDate: 2023-09-12 00:13:10 +0000 dev-qt/qtbase: skip known failing tests on arm32 Again, goal is more or less to get a baseline where things are not completely broken. Unless get general failures not going to worry too much about it. Intentionally skipping everywhere so this does not come back for other arches either. Closes: https://bugs.gentoo.org/914028 Signed-off-by: Ionen Wolkens <ionen@gentoo.org> dev-qt/qtbase/qtbase-6.5.2-r2.ebuild | 3 +++ dev-qt/qtbase/qtbase-6.5.9999.ebuild | 3 +++ dev-qt/qtbase/qtbase-6.9999.ebuild | 3 +++ 3 files changed, 9 insertions(+) |