tests_meego/ChangeLogHandlerTest.cpp | 2 1 + 1 - 0 !
tests_meego/ChangeLogTest.cpp | 4 2 + 2 - 0 !
tests_meego/NonceStorageTest.cpp | 2 1 + 1 - 0 !
tests_meego/SessionHandlerTest.cpp | 2 1 + 1 - 0 !
tests_meego/SyncTargetTest.cpp | 2 1 + 1 - 0 !
tests_meego/clienttests/ClientSessionHandlerTest.cpp | 2 1 + 1 - 0 !
tests_meego/servertests/ServerCommandHandlerTest.cpp | 2 1 + 1 - 0 !
tests_meego/servertests/ServerSessionHandlerTest.cpp | 2 1 + 1 - 0 !
8 files changed, 9 insertions(+), 9 deletions(-)

 fix hardcoded temporary directory

tests_meego/SyncAgentTest.cpp | 6 3 + 3 - 0 !
1 file changed, 3 insertions(+), 3 deletions(-)

 fix incorrect library version in tests

tests_meego/transporttests/transporttests.pro | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 disable clientworkertest unit tests
 Several unit tests in ClientWorkerTest fail because worker.isConnected()
 returns false. This happens because OBEXClientWorker::process() returns
 prematurely after sending an OBEX CONNECT because OBEX_HandleInput() returns 0
 which according to the libopenobex documentation should only happen in case of
 a timeout but in reality also happens in case of a EAGAIN, EINTR or EWOULDBLOCK
 when reading or writing to the server. In the unit tests this happens due to a
 race condition when the client tries to read a response from the server before
 it is ready. This seems to be more of an issue with libopenobex than with
 syncml since the OBEX_HandleInput() takes a timeout argument and is only
 documented to return 0 in case of exceeding that timeout.

tests_meego/transporttests/transporttests.pro | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 disable obextransporttest unit tests
 The OBEXTransportTest::testClientSend unit test hangs for unknown reasons.

src/ServerAlertedNotification.cpp | 2 1 + 1 - 0 !
src/client/ClientSessionHandler.cpp | 2 1 + 1 - 0 !
2 files changed, 2 insertions(+), 2 deletions(-)

 [patch] src/: fix typos in debug/warning messages.

Signed-off-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>