> > 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 ... cheers, Gerd
