From: Joshua Watt <jpewhacker@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [bitbake-devel][PATCH 0/5] Add cleanup commands for hash equivalence
Date: Fri, 6 Oct 2023 09:36:40 -0600 [thread overview]
Message-ID: <20231006153645.1609760-1-JPEWhacker@gmail.com> (raw)
Adds two new APIs and corresponding `bitbake-hashclient` commands for
the hash equivalence server.
The first command is `remove` (`bitbake-hashclient remove`) and it can
be used to remove database entries that match the specified criteria. It
can be useful to remove entries in the in database that are know to be
no longer valid.
The second command is `clean-unused` (`bitbake-hashclient clean-unused`)
which will remove any database entries that are older than the specified
age and are not referenced by a valid unihash.
[YOCTO #15064]
Joshua Watt (5):
hashserv: Add remove API
bitbake-hashclient: Add remove subcommand
hashserv: Extend get_outhash API to optionally include unihash
hashserv: Add API to clean unused entries
bitbake-hashclient: Add clean-unused subcommand
bitbake/bin/bitbake-hashclient | 22 ++++++++
bitbake/lib/hashserv/client.py | 14 ++++-
bitbake/lib/hashserv/server.py | 93 ++++++++++++++++++++++++++++------
bitbake/lib/hashserv/tests.py | 52 +++++++++++++++++++
4 files changed, 163 insertions(+), 18 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-06 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 15:36 Joshua Watt [this message]
2023-10-06 15:36 ` [bitbake-devel][PATCH 1/5] hashserv: Add remove API Joshua Watt
2023-10-06 15:36 ` [bitbake-devel][PATCH 2/5] bitbake-hashclient: Add remove subcommand Joshua Watt
2023-10-06 15:36 ` [bitbake-devel][PATCH 3/5] hashserv: Extend get_outhash API to optionally include unihash Joshua Watt
2023-10-06 15:36 ` [bitbake-devel][PATCH 4/5] hashserv: Add API to clean unused entries Joshua Watt
2023-10-06 15:36 ` [bitbake-devel][PATCH 5/5] bitbake-hashclient: Add clean-unused subcommand Joshua Watt
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=20231006153645.1609760-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.