[Digikam-devel] 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?