On Tue, May 08, 2018 at 02:54:39PM +0100, Peter Maydell wrote:
On 8 May 2018 at 14:48, Daniel P. Berrangé <address@hidden> wrote:
This test has a couple of threads running, and passes &error_abort to
the qio_channel_socket_readv() function. So I expect that one thread
is closing the socket connection, and the other thread has not yet
shutdown cleanly, so tries to readv on a dead socket triggering the
error_abort. IOW, qio_channel_socket_readv is likely just the symptom
of brokeness somewhere else in the test, not the cause.
That sounds familiar...didn't we have a thread about this a while back?
Yeah, I don't recall if it was related to this particular test, or
another similar situation in a different test.