Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.4.0
-
None
-
Debian GNU/Linux experimental
-
2d4c382f0133da0b56634b96e96e5c0f7ad92a2f
Description
In Debian, we are getting this failure when trying to run tests on some architectures:
PASS : tst_QWebSocket::tst_invalidOrigin() QWARN : tst_QWebSocket::tst_sendTextMessage() QObject::connect: signal not found in QWebSocketServer QWARN : tst_QWebSocket::tst_sendTextMessage() QObject::connect: signal not found in QWebSocketServer FAIL! : tst_QWebSocket::tst_sendTextMessage() 'textMessageReceived.wait(500)' returned FALSE. () Loc: [tst_qwebsocket.cpp(460)] QWARN : tst_QWebSocket::tst_sendBinaryMessage() QObject::connect: signal not found in QWebSocketServer QWARN : tst_QWebSocket::tst_sendBinaryMessage() QObject::connect: signal not found in QWebSocketServer FAIL! : tst_QWebSocket::tst_sendBinaryMessage() 'binaryMessageReceived.wait(500)' returned FALSE. () Loc: [tst_qwebsocket.cpp(534)] FAIL! : tst_QWebSocket::tst_errorString() Compared values are not the same Actual (errorSpy.count()): 0 Expected (1) : 1 Loc: [tst_qwebsocket.cpp(596)]
This happens on powerpc, ppc64el (but not ppc64), and hppa.
The full build logs are available here.