From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Subject: Split archives to new repo - clean kdevops repo
Date: Thu, 28 Mar 2024 11:04:09 -0700 [thread overview]
Message-ID: <ZgWxGY63qZDJeA2U@bombadil.infradead.org> (raw)
At LSFMM long ago we had a discussion about keeping test results
around, back of the napkin calcluation then for fstests end up
with an estimate impact of about 730.40 GiB per year, removing the
good results and only keeping *.bad and *.dmesg for failed tests
was about 456.5 MiB per year, and compressing it ~44 KiB per year.
For 5 filesystems that is about 100 MiB / year.
Well, kdevops is a big fat pig now over 200 MiB, and even though the
above math was conservative it turns out that to make results more
useful for things like an ELK stack, we want to keep good results.
And in practice now git grep'ing is creating a lot of noise.
And so it seems best the experiment to keep results for tests has
come to a crux, and I'd like to suggest we spin off the results into
an optional archive directory per workflow, and we create a fresh
new kdevops git tree from scratch, and move the existing one to
kdevops-history.
The way I'd see this is, we'd look for ~/kdevops-archive/ and if present
a new future 'make kdevops-archive' would add directory symlinks to
workflows/fstests/results/archive/ --> ~/kdevops-archive/workflows/fstests/results/archive/
That would keep things like scripts/workflows/fstests/copy-results.sh
working, we'd just have to check if the directory exist first before
proceeding.
This:
* let's us modify results to contain even *good* results so we can
help ELK stacks which want good results too
* puts the churn of the archive out to a separate tree
* keeps kdevops clean
If this is agreeable, perhaps we can make the switch Monday? Any
opposition to this?
Luis
next reply other threads:[~2024-03-28 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 18:04 Luis Chamberlain [this message]
2024-03-30 11:09 ` Split archives to new repo - clean kdevops repo Jeff Layton
2024-04-03 1:34 ` Luis Chamberlain
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=ZgWxGY63qZDJeA2U@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=kdevops@lists.linux.dev \
/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).