"Aaron M. Ucko" <u...@debian.org> writes: > 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?
> 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) Hi Aaron, I've been looking into this for quite some time. I created an x32 build environment, and the build finished without any problem, I failed to reproduce the segfault. If you could extract a core dump or at least a backtrace from the buildd, I'd gladly check it out. -- Regards, Feri
