From: "Cédric Le Goater" <clg@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Nicholas Piggin <npiggin@gmail.com>,
Harsh Prateek Bora <harshpb@linux.ibm.com>
Subject: Re: [PATCH] tests/functional: Update the ppc64 pseries and pnv tests
Date: Wed, 26 Feb 2025 17:34:05 +0100 [thread overview]
Message-ID: <d1aaf224-ab54-4deb-b97b-65e807e88e1e@redhat.com> (raw)
In-Reply-To: <Z77ZLE8TAQvbfb5k@redhat.com>
Hello,
On 2/26/25 10:04, Daniel P. Berrangé wrote:
> On Wed, Feb 26, 2025 at 08:01:09AM +0100, Thomas Huth wrote:
>> On 26/02/2025 07.54, Cédric Le Goater wrote:
>>> The tests are using a now archived Fedora29 release. Switch to the
>>> most recent Fedora41 release.
>>>
>>> Signed-off-by: Cédric Le Goater <clg@redhat.com>
>>> ---
>>> tests/functional/test_ppc64_powernv.py | 6 +++---
>>> tests/functional/test_ppc64_pseries.py | 6 +++---
>>> 2 files changed, 6 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/tests/functional/test_ppc64_powernv.py b/tests/functional/test_ppc64_powernv.py
>>> index 685e2178ed78..a9da7905366e 100755
>>> --- a/tests/functional/test_ppc64_powernv.py
>>> +++ b/tests/functional/test_ppc64_powernv.py
>>> @@ -18,9 +18,9 @@ class powernvMachine(LinuxKernelTest):
>>> good_message = 'VFS: Cannot open root device'
>>> ASSET_KERNEL = Asset(
>>> - ('https://archives.fedoraproject.org/pub/archive/fedora-secondary/'
>>> - 'releases/29/Everything/ppc64le/os/ppc/ppc64/vmlinuz'),
>>> - '383c2f5c23bc0d9d32680c3924d3fd7ee25cc5ef97091ac1aa5e1d853422fc5f')
>>> + ('https://archives.fedoraproject.org/pub/fedora-secondary/'
>>> + 'releases/41/Everything/ppc64le/os/ppc/ppc64/vmlinuz'),
>>> + 'eca627adbe42437cacea169beeb4c3c12a5cfbca1a6b1ba5218d28139d2143c4')
>>
>> I think we should rather avoid the very latest and greatest Fedora URLs
>> here... they will be invalid in a couple of months after Fedora 43 has been
>> released. And if we keep switching the test assets all the time, this will
>> make it more difficult to bisect regressions in the future.
>
> Neither of the URLs here should change, as both are using the
> archives.fedoraproject.org server which carries all historic
> content.
Indeed but the files below :
https://archives.fedoraproject.org/pub/fedora-secondary/<rel>/
are moved under
https://archives.fedoraproject.org/pub/archive/fedora-secondary/<rel>/
every 2 releases and QEMU tests will break :/
In my tests, I prefer to use the latest FW/Linux images because
HW support should be better, which is always good to exercise a
bit more the QEMU models.
That said, older images (f29) should keep on working too on PPC.
Thanks,
C.
prev parent reply other threads:[~2025-02-26 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 6:54 [PATCH] tests/functional: Update the ppc64 pseries and pnv tests Cédric Le Goater
2025-02-26 7:01 ` Thomas Huth
2025-02-26 7:54 ` Cédric Le Goater
2025-02-26 8:11 ` Thomas Huth
2025-02-26 8:18 ` Cédric Le Goater
2025-02-26 9:04 ` Daniel P. Berrangé
2025-02-26 16:34 ` Cédric Le Goater [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=d1aaf224-ab54-4deb-b97b-65e807e88e1e@redhat.com \
--to=clg@redhat.com \
--cc=berrange@redhat.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).