qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/2] Unit test+fix for problem with QEMU handlin


From: Fam Zheng
Subject: Re: [Qemu-devel] [PATCH 0/2] Unit test+fix for problem with QEMU handling of multiple bind()s to the same port
Date: Tue, 13 Jun 2017 15:21:31 +0800
User-agent: Mutt/1.8.0 (2017-02-23)

On Tue, 06/13 08:42, Knut Omang wrote:
> >   GTESTER tests/test-qht-par
> > ** Failed to assign a port to thread 0 (errno = 111)
> > **
> > ERROR:/tmp/qemu-test/src/tests/test-listen.c:103:listen_compete_nthr: 
> > assertion failed:
> > (strstr(thr[i].errstr, "Failed to listen on socket") != NULL)
> > GTester: last random seed: R02S7bbaabe0e7d7cadb4b06bd43593754ef
> > ** Failed to assign a port to thread 0 (errno = 111)
> > **
> > ERROR:/tmp/qemu-test/src/tests/test-listen.c:103:listen_compete_nthr: 
> > assertion failed:
> > (strstr(thr[i].errstr, "Failed to listen on socket") != NULL)
> > GTester: last random seed: R02S3ef87a7625dc47c6cabe0aeaf2636fd2
> > make: *** [check-tests/test-listen] Error 1
> > make: *** Waiting for unfinished jobs....
> 
> This is a bit odd - an environment issue/limitation with the docker image?
> (I do create a lot of threads and parallel calls here to provoke the original 
> error..)
> 
> According to my man pages neither of the system calls involved ( bind(), 
> listen(),
> getaddrinfo() or socket() ) may return ECONNREFUSED (= 111)  ?
> 
> I'll fix v2 to get some more details from the test here..
> 
> > Broken pipe
> > GTester: last random seed: R02Sb1267c89d00d2ed82064ff85f35be761
> > Could not access KVM kernel module: No such file or directory
> > failed to initialize KVM: No such file or directory
> > Back to tcg accelerator.
> 
> I gather this is just a consequence of the failing test, or another 
> environment issue?

Please ignore the KVM warnings, it's not available in the docker env and
triggers on all patches for now.

Fam



reply via email to

[Prev in Thread] Current Thread [Next in Thread]