qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	avocado-devel <avocado-devel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Problem running functional tests from China
Date: Wed, 24 Feb 2021 10:29:05 -0300	[thread overview]
Message-ID: <b2cef7c0-eff8-b725-20de-443ec253ed48@redhat.com> (raw)
In-Reply-To: <20210224120140.GO6564@kitsune.suse.cz>

Hi,

On 2/24/21 9:01 AM, Michal Suchánek wrote:
> On Wed, Feb 24, 2021 at 12:37:53PM +0100, Philippe Mathieu-Daudé wrote:
>> On 2/24/21 12:06 PM, Michal Suchánek wrote:
>>> On Wed, Feb 24, 2021 at 10:29:15AM +0100, Philippe Mathieu-Daudé wrote:
>>>> Just to inform the files hosted on github don't work when
>>>> testing from China:
>>>> raw.githubusercontent.com resolves to 127.0.0.1
>> Actually not even localhost but 0.0.0.0 :)
>>
>>> And from where does this come from?
>>>
>>> Your local system, your ISP, ... ?
>> Probably the ISP:
>>
> ...
>> I raised that problem not to find a way to bypass an ISP
>> firewall, but to see if there is a way to use another
>> storage for test artifacts so all the community can run
>> the tests.
> I don't think protecting from random network malfunction is something
> the qemu project can do.
>
> That said, downloading the test data during test run does indeed look
> fragile.

For those functional tests, the test data is fetched once and cached 
locally.

The user can also inject files on Avocado's cache directory, by using 
the `assets` sub-command:

---

$ ./build/tests/venv/bin/avocado assets register --help
usage: avocado assets register [-h] [--hash SHA1] name url

positional arguments:
   name         Unique name to associate with this asset.
   url          Path to asset that you would like to register manually.

optional arguments:
   -h, --help   show this help message and exit
   --hash SHA1  SHA1 hash of this asset.

----

More features for managing the cache has been implemented, e.g.:

https://github.com/avocado-framework/avocado/issues/4311

Thanks!

- Wainer

>
> We have the concept of git submodules which is used in qemu extensively
> so the test data could possibly be included directly in the git tree.
>
> The obvious downside is that the current and past test binaries will take
> up disk space for all users that check out the repository, even those
> that don't run the tests.
>
> Thanks
>
> Michal
>



      parent reply	other threads:[~2021-02-24 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24  9:29 Problem running functional tests from China Philippe Mathieu-Daudé
2021-02-24 11:06 ` Michal Suchánek
2021-02-24 11:37   ` Philippe Mathieu-Daudé
2021-02-24 12:01     ` Michal Suchánek
2021-02-24 12:08       ` Daniel P. Berrangé
2021-02-24 12:48         ` Philippe Mathieu-Daudé
2021-02-24 12:57           ` Daniel P. Berrangé
2021-02-24 13:22             ` Michal Suchánek
2021-02-24 13:32             ` Wainer dos Santos Moschetta
2021-02-24 13:29       ` Wainer dos Santos Moschetta [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b2cef7c0-eff8-b725-20de-443ec253ed48@redhat.com \
    --to=wainersm@redhat.com \
    --cc=avocado-devel@redhat.com \
    --cc=msuchanek@suse.de \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).