From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/30274] RFE have fedabipkgdiff prefer debuginfod when available
Date: Sun, 26 Mar 2023 03:18:19 +0000 [thread overview]
Message-ID: <bug-30274-9487-BBJl3H1xkj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30274-9487@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30274
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
fedabipkgdiff does a busy loop on waitpid() on the abipkgdiff child process:
@log_call
def abipkgdiff(cmp_half1, cmp_half2):
[...]
proc = subprocess.Popen(' '.join(cmd), shell=True,
stdout=subprocess.PIPE, stderr=subprocess.PIPE,
universal_newlines=True)
# So we could have done: stdout, stderr = proc.communicate()
# But then the documentatin of proc.communicate says:
#
# Note: The data read is buffered in memory, so do not use this
# method if the data size is large or unlimited. "
#
# In practice, we are seeing random cases where this
# proc.communicate() function does *NOT* terminate and seems to be
# in a deadlock state. So we are avoiding it altogether. We are
# then busy looping, waiting for the spawn process to finish, and
# then we get its output.
#
while True:
if proc.poll() != None:
break
Not sure that interpretation of python docs is correct, but even then, a wee
bit of sleep wouldn't hurt.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-03-26 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 1:40 [Bug default/30274] New: " woodard at redhat dot com
2023-03-26 3:18 ` fche at redhat dot com [this message]
2023-03-26 14:24 ` [Bug default/30274] " woodard 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-30274-9487-BBJl3H1xkj@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).