Created attachment 896223 [details] build.log and emerge --info Believe this is caused by https://github.com/nanomsg/nanomsg/issues/1111 stderr: /usr/lib64/libnanomsg.so.6(+0x17608)[0xffffafc97608] /usr/lib64/libnanomsg.so.6(nn_chunk_size+0xc)[0xffffafc978c0] /usr/lib64/libnanomsg.so.6(nn_recvmsg+0x2b0)[0xffffafc91380] /usr/lib64/libnanomsg.so.6(nn_recv+0x4c)[0xffffafc9147c] /var/tmp/portage/dev-libs/criterion-2.4.1/work/criterion-2.4.1-build/src/libcriterion.so.3(+0x136a0)[0xffffb00336a0] /var/tmp/portage/dev-libs/criterion-2.4.1/work/criterion-2.4.1-build/src/libcriterion.so.3(criterion_run_all_tests+0x300)[0xffffb002c540] /var/tmp/portage/dev-libs/criterion-2.4.1/work/criterion-2.4.1-build/src/libcriterion.so.3(main+0x54)[0xffffb0025874] /usr/lib64/libc.so.6(+0x28244)[0xffffafe98244] /usr/lib64/libc.so.6(__libc_start_main+0x98)[0xffffafe98318] /var/tmp/portage/dev-libs/criterion-2.4.1/work/criterion-2.4.1-build/samples/description.c.bin(+0xb70)[0xaaaaddf20b70] Assertion failed: nn_getl ((uint8_t*) p - sizeof (uint32_t)) == NN_CHUNK_TAG (/var/tmp/portage/dev-libs/nanomsg-1.2.1/work/nanomsg-1.2.1/src/utils/chunk.c:231) Summary of Failures: 1/42 sample / description.c FAIL 0.13s killed by signal 6 SIGABRT 2/42 sample / fixtures.c FAIL 0.12s killed by signal 6 SIGABRT 3/42 sample / log.c FAIL 0.12s killed by signal 6 SIGABRT 4/42 sample / asserts.c FAIL 0.21s killed by signal 6 SIGABRT 6/42 sample / redirect.c FAIL 0.17s killed by signal 6 SIGABRT 7/42 sample / report.c FAIL 0.17s killed by signal 6 SIGABRT 8/42 sample / simple.c FAIL 0.14s killed by signal 6 SIGABRT 9/42 sample / signal.c FAIL 0.16s killed by signal 6 SIGABRT 10/42 sample / skip.c FAIL 0.18s killed by signal 6 SIGABRT 11/42 sample / suites.c FAIL 0.17s killed by signal 6 SIGABRT 12/42 sample / parameterized.c FAIL 0.29s killed by signal 6 SIGABRT 13/42 sample / timeout.c FAIL 0.17s killed by signal 6 SIGABRT 14/42 sample / theories.c FAIL 0.20s killed by signal 6 SIGABRT 15/42 sample / description.cc FAIL 0.17s killed by signal 6 SIGABRT 16/42 sample / fixtures.cc FAIL 0.18s killed by signal 6 SIGABRT 17/42 sample / log.cc FAIL 0.17s killed by signal 6 SIGABRT 18/42 sample / more-suites.cc FAIL 0.16s killed by signal 6 SIGABRT 19/42 sample / asserts.cc FAIL 0.29s killed by signal 6 SIGABRT 20/42 sample / redirect.cc FAIL 0.18s killed by signal 6 SIGABRT 21/42 sample / report.cc FAIL 0.17s killed by signal 6 SIGABRT 22/42 sample / signal.cc FAIL 0.19s killed by signal 6 SIGABRT 23/42 sample / simple.cc FAIL 0.17s killed by signal 6 SIGABRT 24/42 sample / skip.cc FAIL 0.19s killed by signal 6 SIGABRT 25/42 sample / suites.cc FAIL 0.18s killed by signal 6 SIGABRT 26/42 sample / parameterized.cc FAIL 0.31s killed by signal 6 SIGABRT 27/42 unit tests ERROR 0.17s killed by signal 6 SIGABRT 28/42 sample / theories.cc FAIL 0.23s killed by signal 6 SIGABRT 30/42 full / exit.c FAIL 0.22s killed by signal 6 SIGABRT 31/42 full / failmessages.c FAIL 0.23s killed by signal 6 SIGABRT 32/42 full / long-messages.c FAIL 0.19s killed by signal 6 SIGABRT 33/42 full / other-crashes.c FAIL 0.21s killed by signal 6 SIGABRT 34/42 full / with-time.c FAIL 0.19s killed by signal 6 SIGABRT 35/42 full / theories_regression.c FAIL 0.16s killed by signal 6 SIGABRT 36/42 full / exit.cc FAIL 0.14s killed by signal 6 SIGABRT 37/42 full / exception.cc FAIL 0.16s killed by signal 6 SIGABRT 38/42 full / long-messages.cc FAIL 0.11s killed by signal 6 SIGABRT 39/42 full / other-crashes.cc FAIL 0.10s killed by signal 6 SIGABRT 40/42 full / failmessages.cc FAIL 0.15s killed by signal 6 SIGABRT 41/42 full / theories_regression.cc FAIL 0.09s killed by signal 6 SIGABRT 42/42 cram tests FAIL 6.42s exit status 1 Ok: 2 Expected Fail: 0 Fail: 40 Unexpected Pass: 0 Skipped: 0 Timeout: 0
I just got that same problem on amd64 but not while emerging the package, it happened when I tried to run some tests that I had just built for a personal project. The upstream for nanomsg still hasn't published a release so it is still actively a problem (though a patch has been submitted in the issue that has already been linked that looks like it might solve the issue.)
(In reply to Emily Flion from comment #1) > I just got that same problem on amd64 but not while emerging the package, it > happened when I tried to run some tests that I had just built for a personal > project. > > The upstream for nanomsg still hasn't published a release so it is still > actively a problem (though a patch has been submitted in the issue that has > already been linked that looks like it might solve the issue.) If https://github.com/nanomsg/nanomsg/issues/1111#issuecomment-2113151297 works for you, I can add it.
(In reply to Sam James from comment #2) > (In reply to Emily Flion from comment #1) > > I just got that same problem on amd64 but not while emerging the package, it > > happened when I tried to run some tests that I had just built for a personal > > project. > > > > The upstream for nanomsg still hasn't published a release so it is still > > actively a problem (though a patch has been submitted in the issue that has > > already been linked that looks like it might solve the issue.) > > If https://github.com/nanomsg/nanomsg/issues/1111#issuecomment-2113151297 > works for you, I can add it. iirc I tested adding that patch to dev-libs/nanomsg back when I originally reported this and it worked.
(In reply to Sam James from comment #2) > (In reply to Emily Flion from comment #1) > > I just got that same problem on amd64 but not while emerging the package, it > > happened when I tried to run some tests that I had just built for a personal > > project. > > > > The upstream for nanomsg still hasn't published a release so it is still > > actively a problem (though a patch has been submitted in the issue that has > > already been linked that looks like it might solve the issue.) > > If https://github.com/nanomsg/nanomsg/issues/1111#issuecomment-2113151297 > works for you, I can add it. I am not really versed in Gentoo packaging right now so I wouldn't be sure how to test this, but if matoro tested the given patch on amd64 it would sound ok to patch the package with it.
You can use https://wiki.gentoo.org/wiki//etc/portage/patches#Adding_user_patches to try it, FWIW.
(In reply to Sam James from comment #5) > You can use > https://wiki.gentoo.org/wiki//etc/portage/patches#Adding_user_patches to try > it, FWIW. Thanks for the documentation, I tested on my side and it looks like the patch works (at least with my use case.)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=32f70be06d68b63c63e6c2bd704bf943a62f25df commit 32f70be06d68b63c63e6c2bd704bf943a62f25df Author: Sam James <sam@gentoo.org> AuthorDate: 2024-12-27 15:47:47 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-12-27 15:47:47 +0000 dev-libs/nanomsg: fix chunking Pull in a patch which upstream have acked on the upstream bug but not yet merged/put in a release. This fixes criterion's testsuite. Thanks to matoro and emily. Closes: https://bugs.gentoo.org/934665 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/nanomsg/files/nanomsg-1.2.1-chunk.patch | 49 ++++++++++++++++++++++++ dev-libs/nanomsg/nanomsg-1.2.1-r1.ebuild | 40 +++++++++++++++++++ 2 files changed, 89 insertions(+)
