From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <3282f541-c511-d3eb-d4b2-a8ab29c9c3cf@gmail.com> Date: Tue, 7 Jun 2022 17:36:27 +0300 MIME-Version: 1.0 Subject: Re: #KCIDB v9 release References: <8cdcae43-f16f-b286-8bb3-276597d493d5@gmail.com> From: "Nikolai Kondrashov" In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-ID: To: Dmitry Vyukov Cc: kernelci@groups.io, Nikolai.Kondrashov@redhat.com, Guillaume Tucker , "automated-testing@yoctoproject.org" , syzkaller On 6/7/22 17:35, Dmitry Vyukov wrote: > On Tue, 7 Jun 2022 at 15:43, Nikolai Kondrashov wrote: >> >> 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. > > I was just considering possibilities. I am not ready to send excerpts > right now. It will require switching to v4 of the API as well, right? > We are now on 3.0. Yes, that would require switching to the v4 schema. Nick