From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, philmd@linaro.org,
Cleber Rosa <crosa@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [RFC PATCH] tests/avocado: use new rootfs for orangepi test
Date: Wed, 23 Nov 2022 11:03:42 +0100 [thread overview]
Message-ID: <c2120c20-8105-bb78-8e11-6d7ab201f777@redhat.com> (raw)
In-Reply-To: <0dc256bb-d163-66de-a448-389e52c908d3@redhat.com>
On 18/11/2022 15.18, Thomas Huth wrote:
> On 18/11/2022 12.33, Alex Bennée wrote:
>> The old URL wasn't stable. I suspect the current URL will only be
>> stable for a few months so maybe we need another strategy for hosting
>> rootfs snapshots?
>
> Looking at
> http://storage.kernelci.org/images/rootfs/buildroot/buildroot-baseline/
> there are only images for the very last month available - so the new URL
> will likely be invalid in one month already. That's not usable. I think
> you've got to find another solution or remove the test.
Looking at that folder again, it seems there wasn't any more change within
the last week ... so maybe it's not rotating so fast as I was thinking
initially ... thus I guess we could give the patch a try, and if the current
image finally disappears again, we still can think of a different solution.
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2022-11-23 10:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 11:33 [RFC PATCH] tests/avocado: use new rootfs for orangepi test Alex Bennée
2022-11-18 14:18 ` Thomas Huth
2022-11-23 10:03 ` Thomas Huth [this message]
2022-11-23 11:15 ` Philippe Mathieu-Daudé
2022-11-23 11:26 ` Thomas Huth
2022-11-23 14:12 ` Alex Bennée
2022-11-23 18:13 ` Philippe Mathieu-Daudé
2022-11-23 18:49 ` Cédric Le Goater
2022-11-23 23:06 ` Philippe Mathieu-Daudé
2022-11-24 9:32 ` Daniel P. Berrangé
2022-11-24 8:20 ` Thomas Huth
2022-11-24 9:24 ` Daniel P. Berrangé
2022-11-24 9:20 ` Daniel P. Berrangé
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=c2120c20-8105-bb78-8e11-6d7ab201f777@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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).