[Development] CI broken again?

Thu Feb 20 07:21:44 CET 2014

Here's the debug print from the client side of one failure I suspect falls under this category we're discussing here:

QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) not using authentication
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged QAbstractSocket::HostLookupState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged QAbstractSocket::ConnectingState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] not proxying
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] waitForWrite 10000
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketStateChanged QAbstractSocket::ConnectedState
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] _q_controlSocketConnected
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] _q_controlSocketBytesWritten
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state "AuthenticationMethodsSent" bytes available 2
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling parseAuthenticationMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] setting [ "qt-test-server.qt-test-net" : 143 ]
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] sending "size: 33 data: { 5 1 0 3 26 113 116 45 116 101 115 116 45 115 101 114 118 101 114 46 113 116 45 116 101 115 116 45 110 101 116 0 143 }"
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] _q_controlSocketBytesWritten
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification bytes available after parsing: 0
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state "RequestMethodSent" bytes available 148
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling parseRequestMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] parseRequestMethodReply()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] "size: 148 data: { 5 0 0 1 10 212 1 1 215 203 42 32 79 75 32 91 67 65 80 65 66 73 76 73 84 89 32 73 77 65 80 52 114 101 118 49 32 76 73 84 69 82 65 76 43 32 73 68 32 69 78 65 66 76 69 32 83 84 65 82 84 84 76 83 32 76 79 71 73 78 68 73 83 65 66 76 69 68 93 32 100 101 118 45 113 116 45 116 101 115 116 45 115 101 114 118 101 114 32 67 121 114 117 115 32 73 77 65 80 32 118 50 46 52 46 49 50 45 68 101 98 105 97 110 45 50 46 52 46 49 50 45 50 32 115 101 114 118 101 114 32 114 101 97 100 121 13 10 }"
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] got [  QHostAddress( "10.212.1.1" )  : 55243 ]
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) queueing connectionNotification
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification bytes available after parsing: 138
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification more bytes available, calling _q_controlSocketReadNotification() again , read notifications enabled? false
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) setReadNotificationEnabled( true )
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification socks5state "Connected" bytes available 138
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification connected
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] "size: 138 data: { 42 32 79 75 32 91 67 65 80 65 66 73 76 73 84 89 32 73 77 65 80 52 114 101 118 49 32 76 73 84 69 82 65 76 43 32 73 68 32 69 78 65 66 76 69 32 83 84 65 82 84 84 76 83 32 76 79 71 73 78 68 73 83 65 66 76 69 68 93 32 100 101 118 45 113 116 45 116 101 115 116 45 115 101 114 118 101 114 32 67 121 114 117 115 32 73 77 65 80 32 118 50 46 52 46 49 50 45 68 101 98 105 97 110 45 50 46 52 46 49 50 45 50 32 115 101 114 118 101 114 32 114 101 97 100 121 13 10 }"
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification calling emitReadNotification()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) queueing readNotification, setting notification pending to true
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) _q_controlSocketReadNotification bytes available after parsing: 0
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) setReadNotificationEnabled( false )
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) setReadNotificationEnabled( true )
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) QSocks5SocketEnginePrivate::emitReadNotification() not emitting pendingReadNotification; enabled? true , pending? true
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) queueing writeNotification
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [test] checking for canReadLine()
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [test] cannot read line, waiting for ready read
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) [QSocks5] waitForRead 5000
QDEBUG : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) QSocks5SocketEngine(0x99e730) controlSocketError QAbstractSocket::SocketTimeoutError "Network operation timed out"
FAIL!  : tst_QTcpSocket::blockingIMAP(WithSocks5Proxy SSL) 'socket->waitForReadyRead(5000)' returned FALSE. ()
   Loc: [../tst_qtcpsocket.cpp(633)]

Regards,
-Tony

> -----Original Message-----
> From: development-bounces+tony.sarajarvi=digia.com at qt-project.org
> [mailto:development-bounces+tony.sarajarvi=digia.com at qt-project.org] On
> Behalf Of Thiago Macieira
> Sent: 19. helmikuuta 2014 21:26
> To: development at qt-project.org
> Subject: Re: [Development] CI broken again?
> 
> Em qua 19 fev 2014, às 17:43:15, Peter Hartmann escreveu:
> > On 02/19/2014 05:22 PM, Thiago Macieira wrote:
> > > Em qua 19 fev 2014, às 17:20:13, Peter Hartmann escreveu:
> > >> What I think the problem is: We get 2 Socks messages in 1 TCP packet,
> so
> > >> the read notifier only fires once, then we never parse the 2nd Socks
> > >> message.
> > >
> > > What 2 SOCKS messages are those and which command did we send?
> >
> > Unfortunately the codepaste from the Digia test has expired; IIRC they
> > were the 2 responses to our Connect Command:
> >
> > 1. Results(V5): Succeeded, Address Type, Remote Address, Port
> > 2. Command: Connect, Remote Address, Remote Port
> >
> > So I think we need to make the our socket engine parse the 2nd message
> > as well, even without an explicit readyReady().
> 
> There's only one reply per SOCKS request. The server can't send two replies,
> the protocol doesn't support that.
> 
> Did the network self test fail? It should have printed the command dump.
> 
> --
> Thiago Macieira - thiago.macieira (AT) intel.com
>   Software Architect - Intel Open Source Technology Center
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development