diff options
author | Janne Anttila <janne.anttila@digia.com> | 2009-10-02 10:17:38 (GMT) |
---|---|---|
committer | Janne Anttila <janne.anttila@digia.com> | 2009-10-02 10:17:38 (GMT) |
commit | c6eb19412f1d0ffc1d5be1c7451e779c0286e013 (patch) | |
tree | 87f1e7e3a47049f1154401f709864d3070a22951 /doc/src/snippets/code/src_sql_kernel_qsqlindex.cpp | |
parent | ad90350d0ba3971591554f871ec17544be414038 (diff) | |
download | Qt-c6eb19412f1d0ffc1d5be1c7451e779c0286e013.zip Qt-c6eb19412f1d0ffc1d5be1c7451e779c0286e013.tar.gz Qt-c6eb19412f1d0ffc1d5be1c7451e779c0286e013.tar.bz2 |
Disabled QtNetworkSettingsInitializerCode code for Symbian HW.
This code is just causing more problems, than helping us to solve
autotest problems. So initial purpose of this code is against us, why:
qWarning used in this code sto print debug info is not visible in HW
since global static objects are initialized before the QTestLib
initializes the output channel. Running hostname resolving in globab
static object constructir is not very trivial, requiring IAP setup and
all network related code to be executed. Since application environment
is no yet completely running at the time when gloabl static are
costructed, the operation is deemed to fail.
Failing means calling qFatal whcih in essence is causing panic in very
early phase of test execution. This happens also for some QtCore
autotests which have minor dependency to QtNetwork. making the autotest
result to look worse than they actually are.
Reviewed-by: Aleksandar Sasha Babic
Diffstat (limited to 'doc/src/snippets/code/src_sql_kernel_qsqlindex.cpp')
0 files changed, 0 insertions, 0 deletions