From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: Failure for ./tests/functional/arm/test_realview.py
Date: Thu, 28 Aug 2025 08:09:57 +0200 [thread overview]
Message-ID: <4e6b068e-e471-4618-b1fa-bbe20bde1307@redhat.com> (raw)
In-Reply-To: <56800442-3962-43b9-9b87-1b899077a24b@linaro.org>
On 28/08/2025 00.49, Richard Henderson wrote:
> 2025-08-27 21:55:08,729 - qemu-test - INFO - Downloading https://
> archive.openwrt.org/chaos_calmer/15.05.1/realview/generic/openwrt-15.05.1-
> realview-vmlinux-initramfs.elf to /builds/qemu-project/qemu/functional-
> cache/download/
> d3a01037f33e7512d46d50975588d5c3a0e0cbf25f37afab44775c2a2be523e6...
>
> This url is now stale, and is causing the functional-system-debian test to
> fail.
> Do we have an alternate?
Hmm, looks like the server is down, and it's not a usual 404 error. I
thought we'd rather skip the test in such cases (hoping that the server
comes back after a while), but looks like we don't get this error scenario
right... So unless someone knows a different download location for this
asset, I'd suggest to try to fix the asset handling code to skip the test in
such cases instead. And if the server won't be back in a week or two, we
still can consider to remove or replace the test.
BTW: We'd still need a way to enable the asset caching for those runners...
Thomas
next prev parent reply other threads:[~2025-08-28 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 22:49 Failure for ./tests/functional/arm/test_realview.py Richard Henderson
2025-08-28 6:09 ` Thomas Huth [this message]
2025-08-29 8:50 ` Thomas Huth
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=4e6b068e-e471-4618-b1fa-bbe20bde1307@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).