KernelCI discussions
 help / color / mirror / Atom feed
From: "Nikolai Kondrashov" <spbnick@gmail.com>
To: kernelci@groups.io, dvyukov@google.com, Nikolai.Kondrashov@redhat.com
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
	"automated-testing@yoctoproject.org"
	<automated-testing@yoctoproject.org>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: #KCIDB v9 release
Date: Tue, 7 Jun 2022 16:43:01 +0300	[thread overview]
Message-ID: <8cdcae43-f16f-b286-8bb3-276597d493d5@gmail.com> (raw)
In-Reply-To: <CACT4Y+ZKPRZmUhKpSzfH4qQX7EQrN_Nf4038K47PGRd1YM=D8Q@mail.gmail.com>

Hi Dmitri,

On 6/7/22 09:11, Dmitry Vyukov via groups.io wrote:
> 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?

At the moment the dashboard doesn't allow that, but it shouldn't be too hard 
to add support for such filtering. I think I could do that in a couple hours work.

So, please go ahead and send those excerpts, and I'll find some time to add 
that filtering.

Thanks!
Nick

  reply	other threads:[~2022-06-07 13:43 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
2022-06-07 13:43   ` Nikolai Kondrashov [this message]
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=8cdcae43-f16f-b286-8bb3-276597d493d5@gmail.com \
    --to=spbnick@gmail.com \
    --cc=Nikolai.Kondrashov@redhat.com \
    --cc=automated-testing@yoctoproject.org \
    --cc=dvyukov@google.com \
    --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