From: Richard Henderson <richard.henderson@linaro.org>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: More check-functional asset download issues
Date: Wed, 17 Sep 2025 10:49:56 -0700 [thread overview]
Message-ID: <d6b2f2c8-809d-4a94-a18b-2accf10fc5f9@linaro.org> (raw)
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"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/builds/qemu-project/qemu/tests/functional/ppc64/test_e500.py", line 44, in <module>
LinuxKernelTest.main()
File "/builds/qemu-project/qemu/tests/functional/qemu_test/testcase.py", line 251, in main
Asset.precache_suites(path, cache)
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 242, in
precache_suites
Asset.precache_suite(tests)
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 233, in
precache_suite
Asset.precache_suite(test)
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 233, in
precache_suite
Asset.precache_suite(test)
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 235, in
precache_suite
Asset.precache_test(test)
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 222, in
precache_test
asset.fetch()
File "/builds/qemu-project/qemu/tests/functional/qemu_test/asset.py", line 184, in fetch
raise AssetError(self, "Unable to download: %s" % e)
qemu_test.asset.AssetError:
https://github.com/legoater/qemu-ppc-boot/raw/refs/heads/main/buildroot/qemu_ppc64_e5500-2023.11-8-gdcd9f0f6eb-20240104/uImage:
Unable to download: Remote end closed connection without response
ninja: build stopped: subcommand failed.
make: *** [Makefile:168: run-ninja] Error 1
r~
next reply other threads:[~2025-09-17 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 17:49 Richard Henderson [this message]
2025-09-17 18:01 ` More check-functional asset download issues Daniel P. Berrangé
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=d6b2f2c8-809d-4a94-a18b-2accf10fc5f9@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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).