From: AnErrupTion <AnErrupTion@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu(-user-static): update to 7.2.3.
Date: Fri, 09 Jun 2023 18:01:22 +0200 [thread overview]
Message-ID: <20230609160122.vFqHr-2nds8mytF0blUd59VvytWzkAljAaU0kpUO9rA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44310@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
New comment by AnErrupTion on void-packages repository
https://github.com/void-linux/void-packages/pull/44310#issuecomment-1584814543
Comment:
Why is the i686 build failing? It seems like some cryptography/TLS issue...
```
Unexpected error in qcrypto_tls_creds_check_cert_pair() at ../crypto/tlscredsx509.c:362:
/builddir/qemu-7.2.3/build/tests/unit/test-crypto-tlscredsx509: Our own certificate tests/test-crypto-tlscredsx509-certs//server-cert.pem failed validation against tests/test-crypto-tlscredsx509-certs//ca-cert.pem: The certificate is not trusted
[...]
Unexpected error in qcrypto_tls_session_check_certificate() at ../crypto/tlssession.c:299:
/builddir/qemu-7.2.3/build/tests/unit/test-crypto-tlssession: The certificate is not trusted
[...]
ERROR:../tests/unit/test-io-channel-tls.c:224:test_io_channel_tls: assertion failed: (clientHandshake.failed == data->expectClientFail)
[...]
1/95 qemu:unit / test-crypto-tlscredsx509 ERROR 1.77s killed by signal 6 SIGABRT
26/95 qemu:unit / test-crypto-tlssession ERROR 2.48s killed by signal 6 SIGABRT
92/95 qemu:unit / test-io-channel-tls ERROR 6.97s killed by signal 6 SIGABRT
```
next prev parent reply other threads:[~2023-06-09 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 20:07 [PR PATCH] " AnErrupTion
2023-06-08 5:09 ` [PR PATCH] [Updated] " AnErrupTion
2023-06-09 7:05 ` AnErrupTion
2023-06-09 16:01 ` AnErrupTion
2023-06-09 16:01 ` AnErrupTion [this message]
2023-06-09 16:11 ` AnErrupTion
2023-06-10 13:24 ` [PR PATCH] [Updated] " AnErrupTion
2023-06-11 10:05 ` AnErrupTion
2023-06-15 21:44 ` [PR PATCH] [Updated] " AnErrupTion
2023-06-15 21:45 ` AnErrupTion
2023-06-15 22:20 ` AnErrupTion
2023-09-14 1:44 ` github-actions
2023-09-14 4:20 ` [PR PATCH] [Closed]: " AnErrupTion
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=20230609160122.vFqHr-2nds8mytF0blUd59VvytWzkAljAaU0kpUO9rA@z \
--to=anerruption@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).