From: Cleber Rosa <crosa@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH-for-5.2? 1/1] Acceptance tests: bump Fedora to 32
Date: Thu, 3 Dec 2020 12:29:59 -0500 [thread overview]
Message-ID: <20201203172959.GA2792185@localhost.localdomain> (raw)
In-Reply-To: <20201203170233.GK2952498@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]
On Thu, Dec 03, 2020 at 05:02:33PM +0000, Daniel P. Berrangé wrote:
> I think the problem with the Fedora acceptance is that we'll be constantly
> chasing a moving target. Every URL we pick will go away 6-12 months later.
> IOW, while the acceptance test pass today, in 6 months time they'll be
> failing. IOW, switching to F32 doesn't solve the root cause, it just
> pushs the problem down the road for 6 months until F32 is EOL and hits
> the same URL change problem.
>
Just FIY, the tests will not FAIL when the images are removed from the
official locations. This is what happens Today:
JOB ID : e85527a9d75023070f15b833eac0f91f803afc83
JOB LOG : /home/cleber/avocado/job-results/job-2020-12-03T12.21-e85527a/job.log
(1/1) tests/acceptance/boot_linux.py:BootLinuxX8664.test_pc_q35_kvm: CANCEL: Failed to download/prepare boot image (0.33 s)
RESULTS : PASS 0 | ERROR 0 | FAIL 0 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 1
JOB HTML : /home/cleber/avocado/job-results/job-2020-12-03T12.21-e85527a/results.html
JOB TIME : 0.76 s
And *normally*, we'd have 12+ months between updates, that is from
Fedora 31 -> 33, 33 -> 35, etc.
> One way to avoid this is to *not* actually test a current Fedora.
> Instead intentionally point at an EOL Fedora release whose URL has
> already moved to the archive site which is long term stable.
>
So the tradeoff is, a patch every 6 or 12 months, versus using a more
modern guest. With other tests, such as virtiofs_submounts.py,
already depending on the same decision (to avoid multiple guest images
downloaded), I think this tradeoff decision needs more visibility.
IMO, the cost of such a simple patch every 6 or 12 months is very low
provided we'll benefit from the newer guests.
Cheers,
- Cleber.
> 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 :|
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-03 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 21:57 [PATCH-for-5.2? 0/1] Acceptance tests: bump Fedora to 32 Cleber Rosa
2020-12-02 21:57 ` [PATCH-for-5.2? 1/1] " Cleber Rosa
2020-12-03 9:37 ` Philippe Mathieu-Daudé
2020-12-03 16:50 ` Cleber Rosa
2020-12-03 17:02 ` Daniel P. Berrangé
2020-12-03 17:29 ` Cleber Rosa [this message]
2020-12-03 17:36 ` Daniel P. Berrangé
2020-12-03 18:13 ` Willian Rampazzo
2020-12-04 14:08 ` Philippe Mathieu-Daudé
2020-12-04 14:19 ` Daniel P. Berrangé
2020-12-03 10:09 ` [PATCH-for-5.2? 0/1] " Peter Maydell
2020-12-03 16:39 ` Cleber Rosa
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=20201203172959.GA2792185@localhost.localdomain \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).