[Top][All Lists]

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

Re: Problem running functional tests from China

From: Wainer dos Santos Moschetta
Subject: Re: Problem running functional tests from China
Date: Wed, 24 Feb 2021 10:29:05 -0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0


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
Actually not even localhost but :)

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

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.:



- 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.



reply via email to

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