On Tue, Jul 12, 2022 at 11:10:55AM +0200, Miro HronĨok wrote:
Hello,
in this PR:
https://src.fedoraproject.org/rpms/python3.11/pull-request/64
In this Zuul CI job:
https://fedora.softwarefactory-project.io/zuul/build/69d10a1f21e14d959e02...
I see:
Running abidiff inspection... FAIL
In this rpminspect report:
https://fedora.softwarefactory-project.io/rpminspect-report/?url=https://...
(JSON attached)
I see abidiff results as listed as "OK":
"ABI comparison ended unexpectedly."
"Command: abidiff
/var/tmp/rpminspect/local.KjDvKK/before/x86_64/python3-libs-3.11.0~b3-8.fc37.x86_64//usr/lib64/libpython3.11.so.1.0
/var/tmp/rpminspect/local.KjDvKK/after/x86_64/python3-libs-3.11.0~b4-1.fc37.x86_64//usr/lib64/libpython3.11.so.1.0
Functions changes summary: 0 Removed, 0 Changed, 0 Added function Variables
changes summary: 0 Removed, 0 Changed, 0 Added variable Function symbols
changes summary: 0 Removed, 2 Added function symbols not referenced by debug
info Variable symbols changes summary: 0 Removed, 0 Added variable symbol
not referenced by debug info 2 Added function symbols not referenced by
debug info: [A] _PyImport_GetModuleAttr [A] _PyImport_GetModuleAttrString "
What does that even mean?
Why is the result a FAIL when it is listed as OK?
Why is it listed as OK, when it says it ended unexpectedly?
What do I read from the results? Is it OK, not OK, broken?
This is something I ran in to recently and it's currently a known bug that I
have not yet resolved. There is an upstream bug filed if you want to follow
that.
Thanks,
--
David Cantrell <dcantrell(a)redhat.com>
Red Hat, Inc. | Boston, MA | EST5EDT