From: Keith Seitz <keiths@redhat.com>
To: Serhei Makarov <serhei@serhei.io>, "Frank Ch. Eigler" <fche@redhat.com>
Cc: Bunsen <bunsen@sourceware.org>
Subject: Re: bunsen (re)design discussion #1: testrun & branch identifiers, testrun representation
Date: Thu, 7 Apr 2022 09:42:04 -0700 [thread overview]
Message-ID: <6f95aa68-518a-73ca-a4c3-26ae2e2100f3@redhat.com> (raw)
In-Reply-To: <813163ee-3ab5-462c-b2b2-475f77bc3ab1@www.fastmail.com>
On 3/14/22 10:24, Serhei Makarov wrote:
> Given the weak correspondence between Testrun/Testcase objects, we end
> up needing a set of explicit ser/de methods under the hood, just as
> with the JSON representation.
In Sept 2020, I played with this a bit, and I have old (probably stale)
patches lying around to let SQLite do the serialization. The patches
do nothing to replace the JSON or the presented data model.
I reported my initial findings here:
https://sourceware.org/pipermail/bunsen/2020q3/000034.html
If you'd like to peek at that work, I can send it along, but
it is probably quite bit-rot by now.
> My current understanding of the schema would be as follows:
>
> - testruns (testrun_id, project, testlogs_commit_id)
> - ANALYSIS_testrun_kvs (testrun_id, key, value)
> - For analysis results that annotate the original testrun.
> - testrun_kv_types (project, key, schema)
> - We will probably need to store some 'schema' information like this.
> - testcases (testrun_id, name, outcome, subtest_id)
> - subtest_strs (subtest_id, subtest_text)
>
> According to your vision, there would also need to be additional
> tables for analysis results which don't follow the format of testrun
> key-value annotations. Not relevant just yet, and we may need to
> decide a different schema for each category of analysis (diff, grid
> view, regression report, etc.).
I have a prototype schema just to record test data. Bunsen's git repo
is still used to store the actual .sum/.log files and provide commit
IDs to identify a particular testrun, i.e., no bunsne metadata.
Keith
prev parent reply other threads:[~2022-04-07 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:07 Serhei Makarov
2022-03-09 22:25 ` Serhei Makarov
2022-03-10 18:04 ` Frank Ch. Eigler
2022-03-10 20:00 ` Serhei Makarov
2022-03-10 23:00 ` Frank Ch. Eigler
2022-03-14 17:24 ` Serhei Makarov
2022-04-07 16:42 ` Keith Seitz [this message]
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=6f95aa68-518a-73ca-a4c3-26ae2e2100f3@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.org \
--cc=fche@redhat.com \
--cc=serhei@serhei.io \
/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).