[kirigami-addons] [Bug 465244] New: 0.7.0: test suite is failing in `tst_sounds.qml` unit
kloczek
bugzilla_noreply at kde.org
Fri Feb 3 20:23:30 GMT 2023
https://bugs.kde.org/show_bug.cgi?id=465244
Bug ID: 465244
Summary: 0.7.0: test suite is failing in `tst_sounds.qml` unit
Classification: Frameworks and Libraries
Product: kirigami-addons
Version: 0.7.0
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: kloczko.tomasz at gmail.com
CC: carl at carlschwan.eu
Target Milestone: ---
Looks like test suite is failing in one unit
+ cd kirigami-addons-v0.7.0
+ xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu
--output-on-failure --force-new-ctest-process -j48
Internal ctest changing into directory:
/home/tkloczko/rpmbuild/BUILD/kirigami-addons-v0.7.0/x86_64-redhat-linux-gnu
Test project
/home/tkloczko/rpmbuild/BUILD/kirigami-addons-v0.7.0/x86_64-redhat-linux-gnu
Start 1: tst_sounds.qml
1/1 Test #1: tst_sounds.qml ...................***Failed 0.26 sec
********* Start testing of Kirigami *********
Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 13.0.1 20230127 (Red Hat 13.0.1-0)),
fedora 38
PASS : Kirigami::SoundsTest::initTestCase()
FAIL! : Kirigami::SoundsTest::test_click() Compared values are not the same
Actual (): 0
Expected (): 1
Loc:
[/home/tkloczko/rpmbuild/BUILD/kirigami-addons-v0.7.0/autotests/tst_sounds.qml(29)]
FAIL! : Kirigami::SoundsTest::test_hasSounds() Compared values are not the
same
Actual (): false
Expected (): true
Loc:
[/home/tkloczko/rpmbuild/BUILD/kirigami-addons-v0.7.0/autotests/tst_sounds.qml(24)]
PASS : Kirigami::SoundsTest::cleanupTestCase()
Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted, 8ms
********* Finished testing of Kirigami *********
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 0.32 sec
The following tests FAILED:
1 - tst_sounds.qml (Failed)
Errors while running CTest
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list