Bug 2052047 - openblas package's static libraries cause annocheck to never exit [NEEDINFO]
Summary: openblas package's static libraries cause annocheck to never exit
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: annobin
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Cermak
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-08 15:19 UTC by David Cantrell
Modified: 2023-07-17 10:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-17 10:12:48 UTC
Type: Bug
Target Upstream Version:
Embargoed:
nickc: needinfo? (dcantrell)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-111482 0 None None None 2022-02-08 15:25:48 UTC

Description David Cantrell 2022-02-08 15:19:39 UTC
The openblas package is unable to run through annocheck.  Using a recent build, such as https://koji.fedoraproject.org/koji/buildinfo?buildID=1890262 (openblas-0.3.19-3.fc36) I cannot get it to complete annocheck unless I exclude the static libraries.

I am invoking this via rpminspect, which is using the defaults for annocheck.  If I tell rpminspect to ignore /usr/lib/*.a and /usr/lib64/*.a for openblas, it completes fine.

It is consistent across architectures.  I at least checked aarch64, ppc64le, s390x, and x86_64 and it behaves the same way.

I am on Fedora 35 and have annobin-annocheck-10.35 installed.

Comment 1 Nick Clifton 2022-02-08 15:55:08 UTC
Hi David,

  Which openblas rpm(s) trigger this problem ?

  I tried testing openblas-0.3.19-3.fc36.x86_64.rpm and had no problems.

  I also tried testing openblas-static-0.3.19-3.fc36.x86_64.rpm.  This
  took a significant amount of time to complete an annocheck run (55 
  seconds according to the wall clock).  But then there are a *lot* of
  components in the libraries and it looks like all of them have
  problems.

  I was using annobin 10.52 so there is also a possibility that this
  is an already fixed problem.  (Although I do not remember fixing an
  infinite loop issue).

Cheers
  Nick

Comment 2 Florian Weimer 2022-02-08 16:12:49 UTC
Is this an actual infinite loop, or is it perhaps due to a large network transfer? Could this be debuginfod?

Comment 4 Nick Clifton 2023-07-17 10:12:48 UTC
Given that we have no response from the reporter, and no other reports of annocheck going into an infinite loop, I am closing this BZ.

I suspect that Florian's guess that the issue might be debuginfod related is spot on.  It should be noted that annocheck has a command line option to run without using debuginfod (-n or --no-use-debuginfod), which might help if similar problems are encountered in the future.


Note You need to log in before you can comment on or make changes to this bug.