QuerySerializerTest does not know how to print a query; the queries compare different on the build server but equal in local build root. I have no hint what went wrong and debugging on the build server is impractical and unsupported. Reproducible: Always Steps to Reproduce: 1. nepomuk/test/queryserializertest.shell; 2. 3. Actual Results: 1. 1: FAIL! : QuerySerializerTest::testSerialization(a complex one) Compared values are not the same 1: Loc: [/home/abuild/rpmbuild/BUILD/kdelibs-4.10.5/nepomuk/test/queryserializertest.cpp(285)] Expected Results: 1. 1: FAIL! : QuerySerializerTest::testSerialization(a complex one) Compared values are not the same Expected: query Actual: query 1: Loc: [/home/abuild/rpmbuild/BUILD/kdelibs-4.10.5/nepomuk/test/queryserializertest.cpp(285)]
Created attachment 82090 [details] add (QTest ::toString < Nepomuk ::Query ::Query >)
I'm very confused regarding this patch. The test seems to run fine for me, and I'm not sure how adding this - +namespace QTest { template <> inline char * toString (Nepomuk ::Query ::Query const & p) { return toString (p .toString ()); }} fixes the test. Could you please explain the problem a little bit more and provide an explanation about your patch?
The patch does not cause the test to succeed, it makes the failure message readable.
The offending code is in kdelibs and does not belong to the Nepomuk project.
Christopher, are you sure the code is not part of the code handled by Nepomuk developers? We assign bugs by "products", not by repository.
(In reply to comment #5) > Christopher, are you sure the code is not part of the code handled by > Nepomuk developers? We assign bugs by "products", not by repository. I was told it is legacy code written before Nepomuk became a separate project, deprecated and maintained so that old stuff does not break.
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
(In reply to Justin Zobel from comment #7) > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Sorry, entering a bug into the product kdelibs has been disabled.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!