Fam Zheng <f...@redhat.com> writes: > On Fri, 03/13 02:16, Patchew Tool wrote: >> socket_accept failed: Resource temporarily unavailable >> ** >> ERROR:/var/tmp/patchew-test/git/tests/libqtest.c:192:qtest_init: >> assertion failed: (s->fd >= 0 && s->qmp_fd >= 0) >> GTester: last random seed: R02Sa6e2a5d48f79c1916f52824e1b74ecc5 >> socket_accept failed: Resource temporarily unavailable >> ** >> ERROR:/var/tmp/patchew-test/git/tests/libqtest.c:192:qtest_init: >> assertion failed: (s->fd >= 0 && s->qmp_fd >= 0) >> GTester: last random seed: R02Sd05e2b63284437ca347a3e639d127a65 >> blkdebug: Suspended request 'A' >> blkdebug: Resuming request 'A' >> main-loop: WARNING: I/O thread spun for 1000 iterations >> main-loop: WARNING: I/O thread spun for 1000 iterations >> main-loop: WARNING: I/O thread spun for 1000 iterations >> main-loop: WARNING: I/O thread spun for 1000 iterations >> [vmxnet3][WR][vmxnet3_peer_has_vnet_hdr]: Peer has no virtio >> extension. Task offloads will be emulated. >> make: *** [check-qtest-x86_64] Error 1 > > Hmm.. looks like a false alarm, the socket initialization failed but that's > definitely not related to this patch.
I see this occasionally in my own testing. Never got around to harnening the test harness against it.