From: "Dmitry Vyukov" <dvyukov@google.com>
To: Nikolai.Kondrashov@redhat.com
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
kernelci@groups.io,
"automated-testing@yoctoproject.org"
<automated-testing@yoctoproject.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: #KCIDB v9 release
Date: Tue, 7 Jun 2022 08:11:20 +0200 [thread overview]
Message-ID: <CACT4Y+ZKPRZmUhKpSzfH4qQX7EQrN_Nf4038K47PGRd1YM=D8Q@mail.gmail.com> (raw)
In-Reply-To: <a707847a-73a3-af9a-96d1-070cd294dbe8@redhat.com>
On Wed, 1 Dec 2021 at 19:01, Nikolai Kondrashov
<Nikolai.Kondrashov@redhat.com> wrote:
>
> Hello everyone,
>
> I'm proud to announce the release and deployment of KCIDB v9.
>
> Please see the detailed list of changes at
> https://github.com/kernelci/kcidb/releases/tag/v9
>
> Most important changes are listed below.
>
> * Switch to using the new v4 I/O Schema, with following changes:
> * rename "revisions" to "checkouts",
> use origin-generated IDs for them, similar to other objects;
> * add "patchset_hash" field to checkouts,
> remove "publishing_time" field, and
> rename "patch_mboxes" to "patchset_files";
> * rename "description" fields to "comment" everywhere;
> * add "log_url" field to tests;
> * add "log_excerpt" field to all objects;
> See complete schema at
> https://github.com/kernelci/kcidb-io/releases/download/v3/kcidb.v4.schema.json
Hi Nikolai,
If we upload "log_excerpt" with crashes, does the dashboard allow
users to search for substrings in the "log_excerpt"?
Namely, if we upload whole kernel oops as "log_excerpt" (that would be
the intended use, right?), will it be possible to find all crashes
that contain a given function name?
next prev parent reply other threads:[~2022-06-07 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 18:01 #KCIDB v9 release Nikolai Kondrashov
2022-06-07 6:11 ` Dmitry Vyukov [this message]
2022-06-07 13:43 ` Nikolai Kondrashov
2022-06-07 14:35 ` Dmitry Vyukov
2022-06-07 14:36 ` Nikolai Kondrashov
[not found] <16BCB376A7748BB3.24346@groups.io>
2022-01-03 11:49 ` Nikolai Kondrashov
2022-01-05 10:10 ` Nikolai Kondrashov
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='CACT4Y+ZKPRZmUhKpSzfH4qQX7EQrN_Nf4038K47PGRd1YM=D8Q@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=Nikolai.Kondrashov@redhat.com \
--cc=automated-testing@yoctoproject.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=syzkaller@googlegroups.com \
/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 NNTP newsgroup(s).