From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: libabigail@sourceware.org
Subject: [Bug default/29425] New: fedabipkgdiff doesn't prune cache
Date: Thu, 28 Jul 2022 13:59:18 +0000 [thread overview]
Message-ID: <bug-29425-9487@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29425
Bug ID: 29425
Summary: fedabipkgdiff doesn't prune cache
Product: libabigail
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: default
Assignee: dodji at redhat dot com
Reporter: woodard at redhat dot com
CC: libabigail at sourceware dot org
Target Milestone: ---
fedabipkgdiff leaves package files in ls ~/.cache/libabigail after runs. This
can build up and take up a lot of space. I know that mine is a rather extreme
case but I currently have 66Gb of space taken up in
/home/ben/.cache/libabigail/
I think that fedabipkgdiff needs to implement some sort of cache pruning
policy. One heuristic, that may be good enough is if it completes with no error
then it deletes its cache. That way it would be quick and easy to go back and
look at problem cases without downloading the packages again but in the most
likely case, where there are no problems, the cache is kept reasonable.
This seems to be different than: 21568 or maybe something is wrong with the
current behavior.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2022-07-28 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29425-9487@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).