On Tue, Jun 24, 2025 at 12:28 PM Warner Losh <[email protected]> wrote: > > On Tue, Jun 24, 2025 at 10:02 AM Thomas Huth <[email protected]> wrote: > > > > On 22/06/2025 03.46, Warner Losh wrote: > > > > > > > > > On Sat, Jun 21, 2025, 6:01 PM Stefan Hajnoczi <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > On Sat, Jun 21, 2025 at 7:59 PM Stefan Hajnoczi <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > (I forgot to CC qemu-devel) > > > > > > > > > > > Hi, > > > > This might only be temporary, but the CI is getting HTTP 404 Not > > > Found > > > > for the following URL: > > > > > > > https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.1/ > > > FreeBSD-14.1-RELEASE-arm64-aarch64-bootonly.iso <https:// > > > download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.1/ > > > FreeBSD-14.1-RELEASE-arm64-aarch64-bootonly.iso> > > > > > > > > https://gitlab.com/qemu-project/qemu/-/jobs/10424901718#L848 > > > <https://gitlab.com/qemu-project/qemu/-/jobs/10424901718#L848> > > > > > > > > Stefan > > > > > > > > > Time to bump the version to 14.3. > > > > Hmm, while we're used to refresh the CI images for the *host* environments, > > it's rather ugly to see images for the *guests* of the functional tests > > disappear. Maybe we should rather remove that test if the URL is not stable? > > Yes. Most of our images have a shelf life of about a year to 18 months. And > QEMU > should be testing all the 'supported' FreeBSD images, just like for > other projects. > The question becomes how can we, the FreeBSD Project, remove the friction > that's > here now because we timeout / move the older images as they pass out of > support. > > We've also just shifted to a more frequent release cadence, so the > releases have gone > from living for 18-24 months down to just 12. We just released > FreeBSD 14.3, and 14.1 > is only a year old. So what's the best way of dealing with this? We > could have a 14-latest > but the md5 would change... > > So I'm open to making a change, but I need help crafting something > that will work, since > I'm not clever enough to suggest something here.
A test run should be repeatable. If a test passes on a given qemu.git commit then it should continue to pass when run again. Using -latest breaks this property, so let's avoid it. Ideas: 1. FreeBSD provides convenient permanent URLs. 2. QEMU uses a permanent FreeBSD ISO mirror URL instead. Need to find a mirror that is fast and reliable. 3. Someone agrees to regularly update the URL in QEMU's test suite so that breakage isn't exposed. IMO the least desirable solution because an old copy of the test will start failing after 12 months. Stefan
