From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: More check-functional asset download issues
Date: Wed, 17 Sep 2025 19:01:12 +0100 [thread overview]
Message-ID: <aMr3aNpHz1ySnBEg@redhat.com> (raw)
In-Reply-To: <d6b2f2c8-809d-4a94-a18b-2accf10fc5f9@linaro.org>
On Wed, Sep 17, 2025 at 10:49:56AM -0700, Richard Henderson wrote:
> Hi,
>
> We have
>
> https://patchew.org/QEMU/20250829142616.2633254-1-berrange@redhat.com/
>
> in master already, but are still seeing up front failures:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/11391070330
> https://gitlab.com/qemu-project/qemu/-/jobs/11391070366
>
> 2025-09-17 17:26:56,222 - qemu-test - INFO - Downloading https://github.com/legoater/qemu-ppc-boot/raw/refs/heads/main/buildroot/qemu_ppc64_e5500-2023.11-8-gdcd9f0f6eb-20240104/uImage
> to /builds/qemu-project/qemu/functional-cache/download/2478187c455d6cca3984e9dfde9c635d824ea16236b85fd6b4809f744706deda...
> Traceback (most recent call last):
> File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 135, in fetch
> with urllib.request.urlopen(self.url) as resp:
> File "/usr/lib64/python3.9/urllib/request.py", line 214, in urlopen
> return opener.open(url, data, timeout)
> File "/usr/lib64/python3.9/urllib/request.py", line 517, in open
> response = self._open(req, data)
> File "/usr/lib64/python3.9/urllib/request.py", line 534, in _open
> result = self._call_chain(self.handle_open, protocol, protocol +
> File "/usr/lib64/python3.9/urllib/request.py", line 494, in _call_chain
> result = func(*args)
> File "/usr/lib64/python3.9/urllib/request.py", line 1389, in https_open
> return self.do_open(http.client.HTTPSConnection, req,
> File "/usr/lib64/python3.9/urllib/request.py", line 1350, in do_open
> r = h.getresponse()
> File "/usr/lib64/python3.9/http/client.py", line 1377, in getresponse
> response.begin()
> File "/usr/lib64/python3.9/http/client.py", line 320, in begin
> version, status, reason = self._read_status()
> File "/usr/lib64/python3.9/http/client.py", line 289, in _read_status
> raise RemoteDisconnected("Remote end closed connection without"
Sigh, yet another type of exception that urlopen may raise.... this is
why apps end up wanting to catch Exception rather than try to match
all possible specialized subclasses.
We already catch Exception but treat it as a fatal error. I'm inclined
to switch it to be a transient error, so that we don't abort the CI
jobs, just skip tests with msising assets, as we do for HTTP error
codes and for DNS resolution errors.
With 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 :|
prev parent reply other threads:[~2025-09-17 18:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 17:49 More check-functional asset download issues Richard Henderson
2025-09-17 18:01 ` Daniel P. Berrangé [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=aMr3aNpHz1ySnBEg@redhat.com \
--to=berrange@redhat.com \
--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).