Re: Avocado notes from KVM forum 2019

[Cleber Rosa <crosa@redhat.com>]

----- Original Message -----
> From: "Gerd Hoffmann" <kraxel@redhat.com>
> To: "Eduardo Habkost" <ehabkost@redhat.com>
> Cc: avocado-devel@redhat.com, "Philippe Mathieu-Daudé" <philmd@redhat.com>, "qemu-devel" <qemu-devel@nongnu.org>,
> "Wainer dos Santos Moschetta" <wainersm@redhat.com>, "Cleber Rosa" <crosa@redhat.com>
> Sent: Monday, November 25, 2019 9:15:53 AM
> Subject: Re: Avocado notes from KVM forum 2019
> 
> > > 1) Working offline
> > > 
> > > Various people complained Avocado requires online access, and they would
> > > like to use it offline.
> > > 
> > >   Maintainer workflow example is:
> > > 
> > >   - run avocado
> > >   - hack QEMU, build
> > >   - git pull
> > >   - build
> > >   - hack QEMU
> > >   (go offline)
> > >   - hack QEMU
> > >   - build
> > >   - run avocado <- FAILS
> > > 
> > 
> > Ouch.  This shouldn't happen even with no explicit --offline
> > option.  Failure to download artifacts shouldn't make tests
> > report failure.
> 
> Related (and already discussed in the past):  There should be a separate
> "downloads artifacts", especially for larger ones which easily fail to
> download on slower internet links due to hitting the test timeout while
> downloading ...
> 

Hi Gerd,

We listened to you :) and that's an Avocado 73.0 feature (released Friday,
very first bullet point item):

  https://avocado-framework.readthedocs.io/en/73.0/releases/73_0.html

It doesn't cover all use cases, but works as expected for QEMU.  I'm just
waiting the end of the code freeze to bump the Avocado version and have
that in by default.

Thanks!
- Cleber.

> cheers,
>   Gerd
> 
> 
>