qemu-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] tests/avocado: Cancel BootLinux tests in case there is no fr


From: Daniel P . Berrangé
Subject: Re: [PATCH] tests/avocado: Cancel BootLinux tests in case there is no free port
Date: Mon, 7 Mar 2022 18:48:34 +0000
User-agent: Mutt/2.1.5 (2021-12-30)

On Mon, Mar 07, 2022 at 07:31:50PM +0100, Thomas Huth wrote:
> On 07/03/2022 13.50, Daniel P. Berrangé wrote:
> > On Mon, Feb 28, 2022 at 12:43:25PM +0100, Thomas Huth wrote:
> > > The BootLinux tests are currently failing with an ugly python
> > > stack trace on my RHEL8 system since they cannot get a free port
> > > (likely due to the firewall settings on my system). Let's properly
> > > check the return value of find_free_port() instead and cancel the
> > > test gracefully if it cannot get a free port.
> > > 
> > > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > > ---
> > >   Unfortunately, it still takes > 70 seconds for each and every
> > >   tests from tests/avocado/boot_linux.py to get canceled, so
> > >   tests/avocado/boot_linux.py still renders "make check-avocado"
> > >   for me pretty unusable... looking at the implementation of
> > >   find_free_port() in Avocado, I wonder whether there isn't a
> > >   better way to get a free port number in Python? Brute-forcing
> > >   all ports between 1024 and 65536 seems just quite cumbersome
> > >   to me...
> > 
> > Even in the worst case of testing every single port,
> > for INET and INET6 and for STREAM and DGRAM sockets,
> > that find_free_port port completes in a couple of
> > seconds.
> 
> Weird, on my system, the test runs for 70 seconds, just to finally
> discovered that there was no free port available.

Incidentally I'm really suprised you even hit the 'no free port'
scenario. I've never seen that happen unless the machine was
basically doomed due to something leaking open sockets by the
10's of 1000's.

You mention firewall settings above, but I don't think that's
relevant. The find_free_port() call is with no args, so it
gets set to 'address=localhost' which means is_port_free
takes the bind() codepath. The firewall has no interaction
with the bind() codepath in the kernel AFAIK. 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|




reply via email to

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