https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: dev-python/unrardll-0.1.7 fails tests. Discovered on: amd64 (internal ref: tinderbox_musl) System: MUSL-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#CF0015
Created attachment 883561 [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: test_extract (test.test_basic.BasicTests.test_extract) ... Modules/gcmodule.c:113: gc_decref: Assertion "gc_get_refs(g) > 0" failed: refcount is too small Fatal Python error: _PyObject_AssertFailed: _PyObject_AssertFailed
Nothing I can actually do about this...
I would consider giving a full backtrace from gdb on the upstream report.
It's okay, upstream fixed it already. :) https://github.com/kovidgoyal/unrardll/commit/3430ed084a4a4a589dffd5ec58fae59b44b75b41
*** Bug 924041 has been marked as a duplicate of this bug. ***
(In reply to Eli Schwartz from comment #5) > It's okay, upstream fixed it already. :) > > https://github.com/kovidgoyal/unrardll/commit/ > 3430ed084a4a4a589dffd5ec58fae59b44b75b41 If you don't mind, please keep the bug open until the fix is in the tree. That would help to avoid duplicates. Thanks
I closed it as "upstream, out of my hands, and I'm not willing to track it as a bug assigned to me". After I closed it as "upstream, out of my hands, and I'm not willing to track it as a bug assigned to me", upstream fixed it. Because in the process of closing it as "upstream, out of my hands, and I'm not willing to track it as a bug assigned to me" I forwarded the report upstream.
Let's compromise and not assign the bug to me then.
