autotests: don't fail appstream test because of anything on stderr
ClosedPublic

Authored by dfaure on Apr 22 2019, 8:42 PM.

Details

Summary

ERROR_VARIABLE simply means where stderr goes, this includes any qDebug,
which surely doesn't mean failure.

Test Plan

QT_LOGGING_RULES='*=true' ctest. See also CI constantly failing...

Diff Detail

Repository
R290 KPackage
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
dfaure created this revision.Apr 22 2019, 8:42 PM
Restricted Application added a project: Frameworks. · View Herald TranscriptApr 22 2019, 8:42 PM
Restricted Application edited subscribers, added: kde-frameworks-devel; removed: Frameworks. · View Herald Transcript
dfaure requested review of this revision.Apr 22 2019, 8:42 PM
apol accepted this revision.Apr 23 2019, 12:00 AM

Thanks!

This revision is now accepted and ready to land.Apr 23 2019, 12:00 AM
This revision was automatically updated to reflect the committed changes.

Similar to this... is it expected that a glib error makes the test fail? Is the error severe or harmless?

CMake Error at /home/jenkins/workspace/Frameworks/kpackage/kf5-qt5 SUSEQt5.12/autotests/kpackagetoolappstreamtest.cmake:45 (message):
appstream data seems to be imperfect:

(appstreamcli:1306): GLib-GIO-ERROR **: 22:52:44.569: No GSettings schemas
are installed on the system

https://build.kde.org/job/Frameworks/view/Platform%20-%20SUSEQt5.12/job/kpackage/job/kf5-qt5%20SUSEQt5.12/94/testReport/junit/projectroot/autotests/testpackage_appstream/