From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars Rustand <rustand.lars@gmail.com>
Cc: 68399@debbugs.gnu.org
Subject: bug#68399: GnuTLS fails to build for aarch64 in QEMU
Date: Thu, 18 Jan 2024 22:28:53 -0500 [thread overview]
Message-ID: <87wms6j91m.fsf@gmail.com> (raw)
In-Reply-To: <87mstbqbwx.fsf@gmail.com> (Lars Rustand's message of "Fri, 12 Jan 2024 07:52:07 +0100")
Hi,
Lars Rustand <rustand.lars@gmail.com> writes:
[...]
> --- ./src/gl/tests/test-suite.log -------------------------------------------
>
> ===============================================
> GnuTLS 3.8.2: src/gl/tests/test-suite.log
> ===============================================
>
> # TOTAL: 167
> # PASS: 166
> # SKIP: 0
> # XFAIL: 0
> # FAIL: 1
> # XPASS: 0
> # ERROR: 0
>
> .. contents:: :depth: 2
>
> FAIL: test-free
> ===============
>
> qemu-aarch64: ../../linux-user/mmap.c:801: mmap_reserve_or_unmap: Assertion `ret == 0' failed.
> **
> ERROR:../../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
> Bail out! ERROR:../../accel/tcg/cpu-exec.c:532:cpu_exec_longjmp_cleanup: assertion failed: (cpu == current_cpu)
> FAIL test-free (exit status: 127)
That one looks like a probable discrepancy due to QEMU emulation more
than a bug in GnuTLS.
On the other hand, we can see from our CI that an aarch64-linux (actual
hardware) build also failed with:
--8<---------------cut here---------------start------------->8---
FAIL: tls13-resume-x509
=======================
client:668: *** Previous session was NOT resumed
try to resume from session ticket (different cipher order)
server:911: server: session_is_resumed error (1)
try to resume from session ticket (different cipher order)
FAIL tls13-resume-x509 (exit status: 1)
FAIL: tls13-early-data
======================
client:472: client: max_early_data_size mismatch -1 != 1024
server:692: server: Handshake has failed (The TLS connection was non-properly terminated.)
FAIL tls13-early-data (exit status: 1)
[...]
FAIL: dtls-repro-20170915
=========================
negotiating DTLS 1.2 with cli-cert
client: Resource temporarily unavailable, try again.
server: The operation timed out
dtls_try_with_key_mtu:578: Handshake failed
FAIL dtls-repro-20170915 (exit status: 1)
FAIL: resume-with-stek-expiration
=================================
testing tls1.2 resumption
STEK was rotated!
client: Handshake was completed
client: Success: Session was NOT resumed
server: Handshake was completed
server: Success: Session was NOT resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was resumed
server: Handshake was completed
server: Success: Session was resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was resumed
server: Handshake was completed
server: Success: Session was resumed
STEK was rotated!
client: Handshake was completed
client: Success: Session was NOT resumed
server: Handshake was completed
server: Success: Session was NOT resumed
testing tls1.3 resumption
client: Handshake was completed
client: Success: Session was NOT resumed
STEK was rotated!
server: Handshake was completed
server: Success: Session was NOT resumed
client: Handshake was completed
resume_and_close:140: client: Session was not resumed (but should)
STEK was rotated!
server:253: server: Handshake failed: Error in the push function.
FAIL resume-with-stek-expiration (exit status: 1)
--8<---------------cut here---------------end--------------->8---
See: https://ci.guix.gnu.org/build/3170604/details
We should check whether upstream is already tracking these failures and
disable the tests in the meantime in our package of QEMU for this
architecture.
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-19 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 6:52 bug#68399: GnuTLS fails to build for aarch64 in QEMU Lars Rustand
2024-01-19 3:28 ` Maxim Cournoyer [this message]
2024-03-22 8:09 ` Matevz Langus via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wms6j91m.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=68399@debbugs.gnu.org \
--cc=rustand.lars@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).