Bug#886974: kronosnet: FTBFS on x32: api_knet_send_crypto_test segmentation fault

"Aaron M. Ucko" <[email protected]>
Newsgroups gmane.linux.debian.ports.amd64
Message-ID <151572319189.25775.6818980242553132655.reportbug__13939.0373872176$1515723243$gmane$org@ghostwheel.internal.ucko.debian.net>
Source: kronosnet
Version: 1.0-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: [email protected]
Usertags: x32

The build of kronosnet for x32 (admittedly not a release architecture)
ran into errors in api_knet_send_crypto_test per the below excerpts from
https://buildd.debian.org/status/fetch.php?pkg=kronosnet&arch=x32&ver=1.0-1&stamp=1515554249&raw=0

Could you please take a look?

Thanks!

----------------------------------------------------------------------

../../test-driver: line 107:  3419 Segmentation fault      "$@" > $log_file 2>&1
FAIL: api_knet_send_crypto_test
[...]
# TOTAL: 62
# PASS:  61
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: api_knet_send_crypto_test
===============================

Using port 3419
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: Operation not permitted
[knet]: [ERROR] transport: Unable to set local socketpair receive buffer: File name too long
[knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, continuing regardless
[knet]: [ERROR] transport: Failed to set socket buffer via force option 32: Operation not permitted
[knet]: [ERROR] transport: Unable to set local socketpair receive buffer: File name too long
[knet]: [ERROR] transport: DEBIAN_SPECIFIC_KRONOSNET_TEST_MODE is set, continuing regardless
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: Operation not permitted
[...]
[knet]: [ERROR] transport: Failed to set socket buffer via force option 33: Operation not permittFAIL api_knet_send_crypto_test (exit status: 139)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.