[Differential] [Request, 20 lines] D1501: [autotest] Work around "cannot assign undefined" warning
graesslin (Martin Gräßlin)
noreply at phabricator.kde.org
Wed Apr 27 09:03:17 UTC 2016
graesslin created this revision.
graesslin added a reviewer: Plasma.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.
REVISION SUMMARY
If both tests cases in the qml file dialog test are run together, there
is a warning:
file:///opt/qt5/qml/QtQuick/Controls/TextField.qml:638:28: Unable to assign [undefined] to QString
This seems to be caused by destroying the QQmlEngine. Thus this change
keeps one QQmlEngine around and also changes the memory management in
other areas. The ownership of a created component is passed to the
caller, thus it needs to be in a QScopedPointer.
Note: this test asserts on build.kde.org. I'm not able to reproduce the
assert locally, but I think it might be related to this warning.
REPOSITORY
rPLASMAINTEGRATION Integration for Qt applications in Plasma
BRANCH
autotest-memory-management
REVISION DETAIL
https://phabricator.kde.org/D1501
AFFECTED FILES
autotests/kfiledialogqml_unittest.cpp
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: graesslin, Plasma
Cc: plasma-devel, sebas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160427/520930b8/attachment-0001.html>
More information about the Plasma-devel
mailing list