From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: "Thomas Huth" <thuth@redhat.com>,
avocado-devel <avocado-devel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Problem running functional tests from China
Date: Wed, 24 Feb 2021 12:08:19 +0000 [thread overview]
Message-ID: <YDZBsz/FFZtRCokJ@redhat.com> (raw)
In-Reply-To: <20210224120140.GO6564@kitsune.suse.cz>
On Wed, Feb 24, 2021 at 01:01:40PM +0100, 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.
>
> 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.
We explicitly do not want to be distributing / including the
images ourselves, as that makes the QEMU project responsible for
license compliance and thus provision of full & corresponding source.
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 :|
next prev parent reply other threads:[~2021-02-24 12:13 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é [this message]
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
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=YDZBsz/FFZtRCokJ@redhat.com \
--to=berrange@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).