On 10/12/2010 00:44, David Faure wrote:
Yes, this will crash with QT_FATAL_WARNINGS. So? It's good to have a unit
test test border conditions too, even if these conditions lead to
warnings from Qt.
One could try to use QTest::ignoreMessage() [1] to skip expected error
messages.
Does not
Please, find attached my failing tests.
I do not know if this is important or not, I do not have the clucene
backend, and sometimes I can compile soprano, sometimes not.
2010/12/10 Vishesh Handa handa.v...@gmail.com:
Hi.
On Fri, Dec 10, 2010 at 1:03 AM, Jaime jtam...@gmail.com wrote:
You're
On 09/12/2010 17:52, David Faure wrote:
On Tuesday 07 December 2010, Jaime wrote:
Hi,
I've run the kdelibs with the environment variable QT_FATAL_WARNINGS=1,
and the number of failed tests has grown in a noticeable way. (also with 2
crashes).
I guess that less Qt warnings usually means
On Thursday 09 December 2010, Aurélien Gâteau wrote:
On 09/12/2010 17:52, David Faure wrote:
On Tuesday 07 December 2010, Jaime wrote:
Hi,
I've run the kdelibs with the environment variable
QT_FATAL_WARNINGS=1,
and the number of failed tests has grown in a noticeable way.
Hi,
I've run the kdelibs with the environment variable QT_FATAL_WARNINGS=1,
and the number of failed tests has grown in a noticeable way. (also with 2
crashes).
I guess that less Qt warnings usually means less unexpected crashes.
Therefore I suggest to add that variable to the test target,
Jaime wrote:
Hi,
I've run the kdelibs with the environment variable QT_FATAL_WARNINGS=1,
and the number of failed tests has grown in a noticeable way. (also with 2
crashes).
I guess that less Qt warnings usually means less unexpected crashes.
Therefore I suggest to add that