Failed tests: advancedrenametest and dimagehistorygraphtest

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Failed tests: advancedrenametest and dimagehistorygraphtest

Michael G. Hansen
Hi,

I just noticed that advancedrenametest does not pass in the digikam 2.0
branch, because the directory names were changed from 'digikam' to
'core' (see log below). For this special test, maybe start one directory
level deeper in the source tree, to be independent of the name of the
digikam source directory?

dimagehistorygraphtest also fails, see attachment. Also, the test
application does not close after being done, just as the digikam
application - maybe related to bug
https://bugs.kde.org/show_bug.cgi?id=243497 ? Here is a backtrace:

(gdb) bt
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f8c0ba9abeb in QWaitCondition::wait(QMutex*, unsigned long)
() from /usr/local/lib/libQtCore.so.4
#2  0x00007f8c0ba99d1f in QThread::wait(unsigned long) () from
/usr/local/lib/libQtCore.so.4
#3  0x00007f8c0bb51b20 in QFileSystemWatcher::~QFileSystemWatcher() ()
from /usr/local/lib/libQtCore.so.4
#4  0x00007f8c0bb8a73c in QObjectPrivate::deleteChildren() () from
/usr/local/lib/libQtCore.so.4
#5  0x00007f8c0bb90b96 in QObject::~QObject() () from
/usr/local/lib/libQtCore.so.4
#6  0x00007f8c0752d19e in ~DeviceManager (this=0x199a8b0,
__in_chrg=<value optimized out>) at
/c/temp/kde/trunk-svn/kdelibs/solid/solid/ifaces/devicemanager.cpp:32
#7  0x00007f8c0757b3e8 in ~FstabManager (this=0x199a8b0,
__in_chrg=<value optimized out>) at
/c/temp/kde/trunk-svn/kdelibs/solid/solid/backends/fstab/fstabmanager.cpp:134
#8  0x00007f8c07510462 in qDeleteAll<QList<QObject*>::const_iterator>
(begin=..., end=...) at /usr/local/include/QtCore/qalgorithms.h:322
#9  0x00007f8c075102c3 in qDeleteAll<QList<QObject*> > (c=...) at
/usr/local/include/QtCore/qalgorithms.h:330
#10 0x00007f8c0750febe in ~ManagerBasePrivate (this=0x193e150,
__in_chrg=<value optimized out>) at
/c/temp/kde/trunk-svn/kdelibs/solid/solid/managerbase.cpp:54
#11 0x00007f8c07513dbb in ~DeviceManagerPrivate (this=0x193e140,
__in_chrg=<value optimized out>) at
/c/temp/kde/trunk-svn/kdelibs/solid/solid/devicemanager.cpp:62
#12 0x00007f8c07517816 in
QThreadStorage<Solid::DeviceManagerPrivate*>::deleteData (x=0x193e140)
at /usr/local/include/QtCore/qthreadstorage.h:133
#13 0x00007f8c0ba98c14 in QThreadStorageData::finish(void**) () from
/usr/local/lib/libQtCore.so.4
#14 0x00007f8c0bb7c1e7 in
QCoreApplicationPrivate::~QCoreApplicationPrivate() () from
/usr/local/lib/libQtCore.so.4
#15 0x00007f8c0d22c736 in QApplicationPrivate::~QApplicationPrivate() ()
from /usr/local/lib/libQtGui.so.4
#16 0x00007f8c0bb90be5 in QObject::~QObject() () from
/usr/local/lib/libQtCore.so.4
#17 0x00007f8c0d22ddf7 in QApplication::~QApplication() () from
/usr/local/lib/libQtGui.so.4
#18 0x000000000041e394 in main (argc=1, argv=0x7fffac906df8) at
/c/temp/kde/trunk-svn/digikam-git2/core/tests/dimagehistorygraphtest.cpp:59

advancedrenametest log:

(sid-kde-trunk)mike@operator:/c/temp/kdebuild/digikam-git2$
./core/tests/advancedrenametest

********* Start testing of AdvancedRenameWidgetTest *********
Config: Using QTest library 4.7.0, Qt 4.7.0
 

PASS   : AdvancedRenameWidgetTest::initTestCase()
 

PASS   : AdvancedRenameWidgetTest::testFileNameToken()
PASS   : AdvancedRenameWidgetTest::testFileExtensionToken()
PASS   : AdvancedRenameWidgetTest::testFileOwnerToken()
PASS   : AdvancedRenameWidgetTest::testFileGroupToken()
 

FAIL!  : AdvancedRenameWidgetTest::testDirectoryNameToken([dir.])
Compared values are not the same
    Actual (parsed): core.jpg
    Expected (result): digikam.jpg
    Loc:
[/c/temp/kde/trunk-svn/digikam-git2/core/tests/advancedrenametest.cpp(153)]
FAIL!  : AdvancedRenameWidgetTest::testDirectoryNameToken([dir.]_[dir])
Compared values are not the same
    Actual (parsed): core_tests.jpg
    Expected (result): digikam_tests.jpg
    Loc:
[/c/temp/kde/trunk-svn/digikam-git2/core/tests/advancedrenametest.cpp(153)]
PASS   : AdvancedRenameWidgetTest::testNumberToken()
PASS   : AdvancedRenameWidgetTest::testReplaceModifier()
PASS   : AdvancedRenameWidgetTest::testRangeModifier()
PASS   : AdvancedRenameWidgetTest::testDefaultValueModifier()
PASS   : AdvancedRenameWidgetTest::testUppercaseModifier()
PASS   : AdvancedRenameWidgetTest::testLowercaseModifier()
PASS   :
AdvancedRenameWidgetTest::testFirstLetterOfEachWordUppercaseModifier()
PASS   : AdvancedRenameWidgetTest::testChainedModifiers()
PASS   : AdvancedRenameWidgetTest::testEmptyParseString()
PASS   : AdvancedRenameWidgetTest::cleanupTestCase()
Totals: 15 passed, 2 failed, 0 skipped
********* Finished testing of AdvancedRenameWidgetTest *********
(sid-kde-trunk)mike@operator:/c/temp/kdebuild/digikam-git2$


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

dimagehistorygraphtest.log (53K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Failed tests: advancedrenametest and dimagehistorygraphtest

Marcel Wiesweg

> I just noticed that advancedrenametest does not pass in the digikam 2.0
> branch, because the directory names were changed from 'digikam' to
> 'core' (see log below). For this special test, maybe start one directory
> level deeper in the source tree, to be independent of the name of the
> digikam source directory?
>
> dimagehistorygraphtest also fails, see attachment.

Will fix this (the model has changed, the test code is wrong)


> Also, the test
> application does not close after being done, just as the digikam
> application - maybe related to bug
> https://bugs.kde.org/show_bug.cgi?id=243497 ? Here is a backtrace:
>
> (gdb) bt
> #0  pthread_cond_wait@@GLIBC_2.3.2 () at
> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
> #1  0x00007f8c0ba9abeb in QWaitCondition::wait(QMutex*, unsigned long)
> () from /usr/local/lib/libQtCore.so.4
> #2  0x00007f8c0ba99d1f in QThread::wait(unsigned long) () from
> /usr/local/lib/libQtCore.so.4
> #3  0x00007f8c0bb51b20 in QFileSystemWatcher::~QFileSystemWatcher() ()
> from /usr/local/lib/libQtCore.so.4
> #4  0x00007f8c0bb8a73c in QObjectPrivate::deleteChildren() () from
> /usr/local/lib/libQtCore.so.4
> #5  0x00007f8c0bb90b96 in QObject::~QObject() () from
> /usr/local/lib/libQtCore.so.4
> #6  0x00007f8c0752d19e in ~DeviceManager (this=0x199a8b0,
> __in_chrg=<value optimized out>) at
> /c/temp/kde/trunk-svn/kdelibs/solid/solid/ifaces/devicemanager.cpp:32
> #7  0x00007f8c0757b3e8 in ~FstabManager (this=0x199a8b0,
> __in_chrg=<value optimized out>) at
> /c/temp/kde/trunk-svn/kdelibs/solid/solid/backends/fstab/fstabmanager.cpp:1
> 34 #8  0x00007f8c07510462 in qDeleteAll<QList<QObject*>::const_iterator>
> (begin=..., end=...) at /usr/local/include/QtCore/qalgorithms.h:322 #9
> 0x00007f8c075102c3 in qDeleteAll<QList<QObject*> > (c=...) at
> /usr/local/include/QtCore/qalgorithms.h:330

Is this KDE 4.6?


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failed tests: advancedrenametest and dimagehistorygraphtest

Michael G. Hansen
On 01/01/2011 03:57 PM, Marcel Wiesweg wrote:

>> Also, the test
>> application does not close after being done, just as the digikam
>> application - maybe related to bug
>> https://bugs.kde.org/show_bug.cgi?id=243497 ? Here is a backtrace:
>>
>> (gdb) bt
>> #0  pthread_cond_wait@@GLIBC_2.3.2 () at
>> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
>> #1  0x00007f8c0ba9abeb in QWaitCondition::wait(QMutex*, unsigned long)
>> () from /usr/local/lib/libQtCore.so.4
>> #2  0x00007f8c0ba99d1f in QThread::wait(unsigned long) () from
>> /usr/local/lib/libQtCore.so.4
>> #3  0x00007f8c0bb51b20 in QFileSystemWatcher::~QFileSystemWatcher() ()
>> from /usr/local/lib/libQtCore.so.4
>> #4  0x00007f8c0bb8a73c in QObjectPrivate::deleteChildren() () from
>> /usr/local/lib/libQtCore.so.4
>> #5  0x00007f8c0bb90b96 in QObject::~QObject() () from
>> /usr/local/lib/libQtCore.so.4
>> #6  0x00007f8c0752d19e in ~DeviceManager (this=0x199a8b0,
>> __in_chrg=<value optimized out>) at
>> /c/temp/kde/trunk-svn/kdelibs/solid/solid/ifaces/devicemanager.cpp:32
>> #7  0x00007f8c0757b3e8 in ~FstabManager (this=0x199a8b0,
>> __in_chrg=<value optimized out>) at
>> /c/temp/kde/trunk-svn/kdelibs/solid/solid/backends/fstab/fstabmanager.cpp:1
>> 34 #8  0x00007f8c07510462 in qDeleteAll<QList<QObject*>::const_iterator>
>> (begin=..., end=...) at /usr/local/include/QtCore/qalgorithms.h:322 #9
>> 0x00007f8c075102c3 in qDeleteAll<QList<QObject*>  >  (c=...) at
>> /usr/local/include/QtCore/qalgorithms.h:330
>
> Is this KDE 4.6?

Qt 4.7, and KDE trunk sometime before 4.6 beta was released. I didn't
update KDE for quite some time.

Michael
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Failed tests: advancedrenametest and dimagehistorygraphtest

Marcel Wiesweg
> >> /c/temp/kde/trunk-svn/kdelibs/solid/solid/ifaces/devicemanager.cpp:32
> >> #7  0x00007f8c0757b3e8 in ~FstabManager (this=0x199a8b0,
> >> __in_chrg=<value optimized out>) at
> >> /c/temp/kde/trunk-svn/kdelibs/solid/solid/backends/fstab/fstabmanager.cp
> >
> > Is this KDE 4.6?
>
> Qt 4.7, and KDE trunk sometime before 4.6 beta was released. I didn't
> update KDE for quite some time.

I would first assume this is a KDE bug. Looks like the new, HAL-free Solid
backends.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel