https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-python/pythonnet-3.0.3 installs shared libraries that lack NEEDED entries. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-SYSTEM Info about the system: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#MUSL Info about the issue: https://wiki.gentoo.org/wiki/Project:Tinderbox/Common_Issues_Helper#QA0011
Created attachment 883527 [details] build.log build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: /var/tmp/portage/dev-python/pythonnet-3.0.3/temp/environment: line 3122: 10783 Segmentation fault "${@}" Fatal Python error: Segmentation fault tests/test_codec.py::test_sequence Fatal Python error: Aborted
> installs shared libraries that lack NEEDED entries Where is that? All I see in the log is a test failure.
(In reply to Maciej Barć from comment #3) > > installs shared libraries that lack NEEDED entries > > Where is that? All I see in the log is a test failure. It is just an error, thanks for let me know.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4f63fe941833f3cd698a7e7dab7ebf0d2cb3a3c9 commit 4f63fe941833f3cd698a7e7dab7ebf0d2cb3a3c9 Author: Maciej Barć <xgqt@gentoo.org> AuthorDate: 2024-01-30 15:01:52 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2024-01-30 19:58:38 +0000 dev-python/pythonnet: deselect test_sequence Closes: https://bugs.gentoo.org/923231 Signed-off-by: Maciej Barć <xgqt@gentoo.org> dev-python/pythonnet/pythonnet-3.0.3.ebuild | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
Please include some rationale when skipping a test because it segfaulted. Segfaults are serious and need to be investigated, really.
(In reply to Sam James from comment #6) > Please include some rationale when skipping a test because it segfaulted. > > Segfaults are serious and need to be investigated, really. I think musl devs interested in .NET will gladly look into this issue, I could not reproduce on my machine.
Then you should only skip it on musl and add an explanation in the commit message and comment? And ideally ask some musl people to look..
In fact, didn't vimproved mention lots of musl segfaults since the Patchelf hack?
(In reply to Sam James from comment #9) > In fact, didn't vimproved mention lots of musl segfaults since the Patchelf > hack? I know nothing about that. That would be quite interesting.
