From: Fabiano Rosas <farosas@suse.de>
To: Thomas Huth <thuth@redhat.com>, Ani Sinha <anisinha@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: artifact download for qtest
Date: Mon, 08 Jun 2026 16:13:02 -0300 [thread overview]
Message-ID: <87v7bs6e2p.fsf@suse.de> (raw)
In-Reply-To: <f2516211-6fbc-4714-b674-4276464f94ff@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> On 30/05/2026 16.56, Ani Sinha wrote:
>> Hi,
>>
>> I am trying to write a qtest for which I need an IGVM file. I have the
>> file, about 54 MiB in size.
>
> 54 MiB is quite big, I agree that we likely don't want to check that into
> the main repository, especially if it is for a test only...
> (BTW, what's its compressed size?)
>
>> Instead of committing this IGVM binary
>> file with the test, I wanted to check if I can put it somewhere, say
>> in a gitlab repo and then make the test download it. This would be
>> similar to asset downloads for functional tests. No this test cannot
>> be a python functional test. I am wondering if anyone has faced this
>> situation before and what the best way to solve this problem is.
>
> I'm not maintaining the qtests anymore, but I assume that there is no
> interest in duplicating all the asset downloading logic there.
>
It would be nice if we could extract the existing code into a little
asset library that could be invoked from the other test frameworks.
> What's the exact reason why you cannot do it as a functional test instead?
> You could maybe also start the qemu binary there with "-accel qtest -qtest
> ..." to fake a qtest environment - a little bit cumbersome, but certainly
> doable, I think.
>
> Thomas
next prev parent reply other threads:[~2026-06-08 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-30 14:56 artifact download for qtest Ani Sinha
2026-06-08 17:13 ` Thomas Huth
2026-06-08 19:13 ` Fabiano Rosas [this message]
2026-06-08 19:30 ` Daniel P. Berrangé
2026-06-08 20:02 ` Fabiano Rosas
2026-06-09 2:24 ` Ani Sinha
2026-06-09 3:46 ` Ani Sinha
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=87v7bs6e2p.fsf@suse.de \
--to=farosas@suse.de \
--cc=anisinha@redhat.com \
--cc=berrange@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.