From: "Dmitry Vyukov" <dvyukov@google.com>
To: Nikolai Kondrashov <spbnick@gmail.com>
Cc: kernelci@groups.io, syzkaller <syzkaller@googlegroups.com>,
"Iñaki Malerba" <imalerba@redhat.com>,
"Vishal Bhoj" <vishal.bhoj@linaro.org>,
"Alice Ferrazzi" <alicef@gentoo.org>,
automated-testing@lists.yoctoproject.org,
"Cristian Marussi" <cristian.marussi@arm.com>,
"Tim Bird" <Tim.Bird@sony.com>,
"Johnson George" <Johnson.George@microsoft.com>,
"Veronika Kabatova" <vkabatov@redhat.com>,
"Guillaume Tucker" <guillaume.tucker@collabora.com>
Subject: Re: #KCIDB: Publishing known issues
Date: Sat, 2 Jul 2022 09:59:58 +0200 [thread overview]
Message-ID: <CACT4Y+ZkB=ptctWusAxpjBv_iFJX6OeBgN7DSp+2m6eLHBKufQ@mail.gmail.com> (raw)
In-Reply-To: <2d739264-6ece-1c8a-30a0-c1d96a8a8e62@gmail.com>
On Fri, 1 Jul 2022 at 17:05, Nikolai Kondrashov <spbnick@gmail.com> wrote:
>
> On 7/1/22 17:11, Dmitry Vyukov wrote:
> > wOn Fri, 1 Jul 2022 at 14:41, Nikolai Kondrashov <spbnick@gmail.com> wrote:
> >> There's obviously lots and lots more to think about and discuss regarding
> >> "known issues", but please tell me what you think about this particular
> >> aspect. Everything else is welcome too, of course :)
> >
> > Maybe I am missing something, but have you considered making the KCIDB
> > server assign these versions to take this burden from all clients?
> > Users will effectively "modify" entities, except that KCIDB won't
> > actually modify but rather insert new versions. The version can be
> > precise-enough timestamp as you mentioned.
>
> Thank you for your prompt response, and for a good question, Dmitry!
>
> Yes, I considered that for a while, from various angles. Yes, that would be
> simpler for submitters in many cases.
>
> However, it will make the KCIDB protocol more complex (both to understand and
> to implement) by introducing different behavior for different types of objects.
>
> It will force KCIDB to implement comparing issue parameters/contents, instead
> of just comparing version numbers, in order to avoid useless retriage when the
> same issue is submitted multiple times without changes. E.g. when related
> issues are simply submitted together with test results for every revision.
>
> It will also either force KCIDB to introduce global synchronization for
> reliable version number generation, or to use mostly de-synchronized, but
> unreliable timestamp-based versions for *all* submitters, regardless whether
> they can actually do better or not. In this way, this tradeoff is similar to
> having submitters generate their own object IDs.
On the syzbot side we fully control database schema and code, so
adding bug versions should not be a problem at least for major bug
status changes.
next prev parent reply other threads:[~2022-07-02 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 12:41 #KCIDB: Publishing known issues Nikolai Kondrashov
2022-07-01 14:11 ` Dmitry Vyukov
2022-07-01 15:05 ` Nikolai Kondrashov
2022-07-02 7:59 ` Dmitry Vyukov [this message]
2022-07-02 14:02 ` 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+ZkB=ptctWusAxpjBv_iFJX6OeBgN7DSp+2m6eLHBKufQ@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=Johnson.George@microsoft.com \
--cc=Tim.Bird@sony.com \
--cc=alicef@gentoo.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=cristian.marussi@arm.com \
--cc=guillaume.tucker@collabora.com \
--cc=imalerba@redhat.com \
--cc=kernelci@groups.io \
--cc=spbnick@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=vishal.bhoj@linaro.org \
--cc=vkabatov@redhat.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).