Bug 378212 - Threaded ConverterTest::testCurrency() fails
Summary: Threaded ConverterTest::testCurrency() fails
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kunitconversion
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.32.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: John Layt
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-28 17:52 UTC by h.goebel
Modified: 2022-11-05 16:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description h.goebel 2017-03-28 17:52:37 UTC
The test-case ConverterTest::testCurrency(), which was converted to run threaded just for the last release, fails:

********* Start testing of ConverterTest *********
Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 4.9.4)
PASS   : ConverterTest::initTestCase()
PASS   : ConverterTest::testCategory()
PASS   : ConverterTest::testUnits()
PASS   : ConverterTest::testConvert()
PASS   : ConverterTest::testInvalid()
QWARN  : ConverterTest::testCurrency() Type conversion already registered from type QPair<QByteArray,QByteArray> to type QtMetaTypePrivate::QPairVariantInterfaceImpl
QWARN  : ConverterTest::testCurrency() Type conversion already registered from type QSharedPointer<QNetworkSession> to type QObject*
FAIL!  : ConverterTest::testCurrency() 'threads.at(i)->number > 100' returned FALSE. ()
   Loc: [/tmp/guix-build-kunitconversion-5.32.0.drv-0/kunitconversion-5.32.0/autotests/convertertest.cpp(101)]
PASS   : ConverterTest::cleanupTestCase()
Totals: 6 passed, 1 failed, 0 skipped, 0 blacklisted, 163ms
********* Finished testing of ConverterTest *********

Running in a GNU Guix build environment.
Comment 1 Justin Zobel 2022-11-03 01:39:49 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 h.goebel 2022-11-05 16:19:02 UTC
This specific error is gone in 5.96