From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tomas Volf <~@wolfsden.cz>
Cc: 73664@debbugs.gnu.org
Subject: [bug#73664] [PATCH] gnu: libtorrent-rasterbar: Work around hang in test_ssl.
Date: Tue, 17 Dec 2024 14:08:22 +0900 [thread overview]
Message-ID: <87a5cusxq1.fsf@gmail.com> (raw)
In-Reply-To: <b318e317dab97a658b90669a49edc79247716c87.1728231109.git.~@wolfsden.cz> (Tomas Volf's message of "Sun, 6 Oct 2024 18:11:49 +0200")
Hello!
Tomas Volf <~@wolfsden.cz> writes:
> test_ssl does sometimes hang (at least when executed under faketime). It is
> somewhat unlikely to happen, and (on my machine) required a build with
> --rounds=32 to reproduce it.
Also worth adding on top of my previous reply, when trying this out, I
got a failure:
--8<---------------cut here---------------start------------->8---
[...]
MALICIOUS PEER TEST: valid-certificate valid-SNI-hash invalid-bittorrent-hash port: 35161
set_password_callback
use_certificate_file "../ssl/peer_certificate.pem"
use_private_key_file "../ssl/peer_private_key.pem"
use_tmp_dh_file "../ssl/dhparams.pem"
connecting 127.0.0.1:35161
SNI: e300afcc0aa67a459ec14862a4d0bf930060167a
SSL handshake
bittorrent handshake
00:00:00.010: ses1: [log] *** peer SSL handshake done [ ip: 127.0.0.1:44976 ec: certificate verify failed (SSL routines) socket: SSL/TCP ]
read bittorrent handshake
00:00:00.010: ses1: [peer_error] - peer [ 127.0.0.1:44976 client: Unknown ] peer error [ssl_handshake] [asio.ssl]: certificate verify failed (SSL routines)
--- peer_errors: 6 ssl_disconnects: 6
failed to read bittorrent handshake: sslv3 alert bad certificate (SSL routines)
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 405.71 sec
The following tests FAILED:
75 - test_ssl (Failed)
Errors while running CTest
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "faketime" arguments: ("2022-10-24" "ctest" "-R" "^test_ssl$" "-j" "1" "--timeout" "240" "--repeat" "until-pass:5" "--output-on-failure") exit-status: 8 term-signal: #f stop-signal: #f>
phase `check' failed after 1154.0 seconds
command "faketime" "2022-10-24" "ctest" "-R" "^test_ssl$" "-j" "1" "--timeout" "240" "--repeat" "until-pass:5" "--output-on-failure" failed with status 8
build process 18 exited with status 256
builder for `/gnu/store/hkji5nzsa32jngg7kii9bg9ch9kdvs84-libtorrent-rasterbar-2.0.10.drv' failed with exit code 1
build of /gnu/store/hkji5nzsa32jngg7kii9bg9ch9kdvs84-libtorrent-rasterbar-2.0.10.drv failed
View build log at '/var/log/guix/drvs/hk/ji5nzsa32jngg7kii9bg9ch9kdvs84-libtorrent-rasterbar-2.0.10.drv'.
--8<---------------cut here---------------end--------------->8---
--
Thanks,
Maxim
prev parent reply other threads:[~2024-12-17 5:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 16:11 [bug#73664] [PATCH] gnu: libtorrent-rasterbar: Work around hang in test_ssl Tomas Volf
2024-12-17 1:20 ` Maxim Cournoyer
2024-12-17 5:08 ` Maxim Cournoyer [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=87a5cusxq1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=73664@debbugs.gnu.org \
--cc=~@wolfsden.cz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.