public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29693] clang-libs from f37 fails self test with 2.1
Date: Thu, 23 Mar 2023 23:41:21 +0000	[thread overview]
Message-ID: <bug-29693-9487-mgy8qDvUQH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29693-9487@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29693

--- Comment #3 from Ben Woodard <woodard at redhat dot com> ---
This one seems to be behaving oddly. Most other fedabipkgdiff launch abipkgdiff
and you can see the amount of memory shoot up as it consumes the corpus. Then
that finishes and it moves onto the next package and finally terminates.

clang-libs did that but the python code in fedabipkgdiff seemed to get stuck in
a tight loop after the abipkgdiffs ran and it just continues running at 100%
CPU but I don't think it is doing much real work because it is only using 0.1%
of memory. So I think something is going wrong in the fedabipkgdiff python.

This is with the current trunk as of:

commit a8a4ca8862959e9fede1b4878469681b8fadeb74 (HEAD -> master, origin/master,
origin/HEAD)
Author: Dodji Seketeli <dodji@redhat.com>
Date:   Wed Mar 22 15:42:43 2023 +0100

    abipkgdiff: Fix a typo

            * tools/abipkgdiff.cc (compare_to_self): Fix a typo.

    Signed-off-by: Dodji Seketeli <dodji@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-23 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14 22:14 [Bug default/29693] New: " woodard at redhat dot com
2022-10-14 22:15 ` [Bug default/29693] " woodard at redhat dot com
2022-10-25 17:01 ` woodard at redhat dot com
2023-03-23 21:13 ` woodard at redhat dot com
2023-03-23 23:41 ` woodard at redhat dot com [this message]
2023-03-24 16:20 ` woodard at redhat dot com
2023-03-31 22:46 ` [Bug default/29693] clang-libs from f37 fails self test with pre-2.3 trunk woodard at redhat dot com
2023-04-11 14:51 ` dodji at redhat dot com
2023-05-17 15:36 ` dodji at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29693-9487-mgy8qDvUQH@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libabigail@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).